Selection of time-domain resource allocation tables

ABSTRACT

According to certain embodiments, a user equipment, UE, is operable for multiple sub-carrier spacing values. The UE comprises memory operable to store instructions and processing circuitry operable to execute the instructions, whereby the UE is operable to determine one of a plurality of time-domain resource allocation tables based on first information received from a network node. The first information comprises a Radio Network Temporary Identifier, RNTI. The UE is operable to determine a time-domain resource allocated to the UE for transmission or reception of a wireless signal based on the determined one of the plurality of time-domain resource allocation tables and second information received from the network node. The second information comprises a time-domain resource allocation field value received in downlink control information, DCI. The UE is further operable to transmit or receive the wireless signal using the determined time-domain resource.

RELATED APPLICATIONS

This application is a continuation, under 35 U.S.C. § 120 of Ser. No.17/112,275 filed on Dec. 4, 2020 which is a continuation, under 35U.S.C. § 120 of Ser. No. 16/848,187 filed on Apr. 14, 2020 which is acontinuation, under 35 U.S.C. § 120 of Ser. No. 16/193,063 filed on Nov.16, 2018 which claims priority to U.S. Provisional Patent ApplicationNo. 62/587,524 filed Nov. 17, 2017, each of which is hereby incorporatedby reference in its entirety.

TECHNICAL FIELD

Certain embodiments of the present disclosure relate, in general, towireless communications and, more specifically, to the selection oftime-domain resource allocation tables.

BACKGROUND

New Radio (NR) will support a bitfield in the downlink controlinformation (DCI) to select the time-domain resource allocation for thephysical uplink shared channel (PUSCH) and physical downlink sharedchannel (PDSCH) out of preconfigured entries in a table. Each entry inthe table specifies a starting orthogonal frequency divisionmultiplexing (OFDM) symbol and length in OFDM symbols of the allocation.Note that the starting OFDM symbol can be expressed either relative tothe scheduling physical downlink control channel (PDCCH)/control channelresource set (CORESET) symbol(s) or in absolute OFDM symbol numberwithin a slot or subframe.

SUMMARY

There currently exist certain challenge(s). Although, NR is veryflexible, for example, in that NR supports different ways how todistribute system information and supports slot-based transmissions andnon-slot-based transmissions, using a single time-domain resourceallocation table is very limiting and can restrict scheduling in manycases. One possible solution would be to increase the resourceallocation table size and by that enable more time-domain resourceallocations. However, a drawback of that solution would be an increaseddownlink control information (DCI) size because more bits are needed toselect an appropriate resource allocation.

Certain aspects of the present disclosure and their embodiments mayprovide solutions to these or other challenges. According to certainembodiments, a wireless device (e.g., user equipment, UE) is configuredwith multiple time-domain resource allocation tables. Which table to useis implicitly derived from other information available at both thenetwork node (e.g., gNB) and the wireless device. Examples of this otherinformation could be a Radio Network Temporary Identifier (RNTI),information contained in the DCI, which DCI format has been used forscheduling, which CORESET/search space has been used for scheduling, ifthe transmission is slot-based or non-slot-based, carrier aggregationrelated information, bandwidth part related information, slot format,and/or information indicating numerology (e.g., a cyclic prefix, an OFDMsubcarrier spacing, etc.). According to certain embodiments, if thetime-domain resource allocation is used in scheduling of systeminformation (e.g., remaining minimum system information (RMSI)), the waysystem information is distributed (non-slot-based transmission vs.slot-based transmission) determines which table to use. According tocertain embodiments, a wireless device configured with multipletime-domain resource allocation tables derives which table to use frominformation available at the wireless device and selects an entry out ofthat table based on an explicit bit field in the DCI that may bereferred to as the time-domain resource allocation field.

According to certain embodiments a wireless device comprises memory andprocessing circuitry. The memory is operable to store instructions andthe processing circuitry is operable to execute the instructions,whereby the wireless device is operable to determine one of a pluralityof time-domain resource allocation tables based on first informationreceived from a network node. Based on the determined one of theplurality of time-domain resource allocation table and secondinformation received from the network node, the wireless device isoperable to determine a time-domain resource allocated to the wirelessdevice for transmission or reception of a wireless signal. The secondinformation is different from the first information.

According to certain embodiments, a method performed by a wirelessdevice comprises determining one of a plurality of time-domain resourceallocation tables based on first information received from a networknode. The method further comprises determining a time-domain resourceallocated to the wireless device for transmission or reception of awireless signal based on the determined one of the plurality oftime-domain resource allocation tables and second information receivedfrom the network node. The second information is different from thefirst information.

According to certain embodiments, a computer program comprisesinstructions which, when executed by at least one processor of awireless device, causes the wireless device to determine one of aplurality of time-domain resource allocation tables based on firstinformation received from a network node and determine a time-domainresource allocated to the wireless device for transmission or receptionof a wireless signal based on the determined one of the plurality oftime-domain resource allocation tables and second information receivedfrom the network node. The second information is different from thefirst information. In some embodiments, a carrier containing thecomputer program is one of an electronic signal, optical signal, radiosignal, or computer readable storage medium.

According to certain embodiments a wireless device is operable todetermine one of a plurality of time-domain resource allocation tablesbased on first information received from a network node. Based on thedetermined one of the plurality of time-domain resource allocation tableand second information received from the network node, the wirelessdevice is operable to determine a time-domain resource allocated to thewireless device for transmission or reception of a wireless signal. Thesecond information is different from the first information.

The above-described wireless device, method performed by a wirelessdevice, and/or computer program may each include one or more additionalfeatures, such as any one or more of the following features:

In some embodiments, the second information comprises a time-domainresource allocation field value received in DCI.

In some embodiments, the one of the plurality of time-domain resourceallocation tables determined based on the first information comprises aplurality of entries, and the second information indicates which of theplurality of entries to use to determine the time-domain resourceallocated to the wireless device.

In some embodiments, the time-domain resource allocation tables comprisedifferent combinations of starting OFDM symbol position and duration inOFDM symbols for the time-domain resource allocation.

In some embodiments, the plurality of time-domain resource allocationtables relates to time-domain resource allocation for PUSCH or forPDSCH.

In some embodiments, the plurality of time-domain resource allocationtables comprises at least one of pre-defined tables with default valuesfor the time domain resource allocation and RRC configured tables. Thatis, the plurality of time-domain resource allocation tables comprisespre-defined tables with default values for the time domain resourceallocation and/or RRC configured tables.

In some embodiments, the first information comprises a Radio NetworkTemporary Identifier, RNTI.

In some embodiments, the first information comprises informationindicating a search space related to a control channel used to schedulethe wireless signal.

In some embodiments, the first information comprises information relatedto a CORESET used to schedule the wireless signal.

In some embodiments, the first information comprises information relatedto bandwidth part.

In some embodiments, the first information comprises information thatindicates a slot format.

In some embodiments, the first information comprises a cyclic prefix, anOFDM subcarrier spacing, or other information indicating numerology.

In some embodiments, the wireless signal is transmitted or receivedusing the determined time-domain resource.

According to certain embodiments, a network node comprises memory andprocessing circuitry. The memory is operable to store instructions andthe processing circuitry is operable to execute the instructions,whereby the network node is operable to determine a time-domain resourceto allocate to a wireless device for transmission or reception of awireless signal. The network node is further operable to send thewireless device first information from which the wireless devicedetermines one of a plurality of time-domain resource allocation tablesand second information from which the wireless device determines thetime-domain resource based on the determined one of the plurality oftime-domain resource allocation tables. The second information isdifferent from the first information.

According to certain embodiments, method performed by a network nodecomprises determining a time-domain resource to allocate to a wirelessdevice for transmission or reception of a wireless signal. The methodfurther comprises sending the wireless device first information fromwhich the wireless device determines one of a plurality of time-domainresource allocation tables and second information from which thewireless device determines the time-domain resource based on thedetermined one of the plurality of time-domain resource allocationtables. The second information is different from the first information.

According to certain embodiments, a computer program comprisesinstructions which, when executed by at least one processor of a networknode, cause the network node to determine a time-domain resource toallocate to a wireless device for transmission or reception of awireless signal. The instructions further cause the network node to sendthe wireless device first information from which the wireless devicedetermines one of a plurality of time-domain resource allocation tablesand second information from which the wireless device determines thetime-domain resource based on the determined one of the plurality oftime-domain resource allocation tables. The second information isdifferent from the first information. In some embodiments, a carriercontaining the computer program is one of an electronic signal, opticalsignal, radio signal, or computer readable storage medium.

According to certain embodiments, a network node is operable todetermine a time-domain resource to allocate to a wireless device fortransmission or reception of a wireless signal. The network node isfurther operable to send the wireless device first information fromwhich the wireless device determines one of a plurality of time-domainresource allocation tables and second information from which thewireless device determines the time-domain resource based on thedetermined one of the plurality of time-domain resource allocationtables. The second information is different from the first information.

The above-described network node, method performed by a network node,and/or computer program may each include one or more additionalfeatures, such as any one or more of the following features:

In some embodiments, the second information comprises a time-domainresource allocation field value sent in DCI.

In some embodiments, the one of the plurality of time-domain resourceallocation tables comprises a plurality of entries. The secondinformation indicates which of the plurality of entries the wirelessdevice should use to determine the time-domain resource.

In some embodiments, the time-domain resource allocation tables comprisedifferent combinations of starting OFDM symbol position and duration inOFDM symbols for the time-domain resource allocation.

In some embodiments, the plurality of time-domain resource allocationtables relates to time-domain resource allocation for PUSCH or forPDSCH.

In some embodiments, the plurality of time-domain resource allocationtables comprises pre-defined tables with default values for the timedomain resource allocation and/or RRC configured tables.

In some embodiments, the first information comprises an RNTI.

In some embodiments, the first information comprises informationindicating a search space related to a control channel used to schedulethe wireless signal.

In some embodiments, the first information comprises information relatedto a CORESET used to schedule the wireless signal.

In some embodiments, the first information comprises information relatedto bandwidth part.

In some embodiments, the first information comprises information thatindicates a slot format.

In some embodiments, the first information comprises a cyclic prefix, anOFDM subcarrier spacing, or other information indicating numerology.

In some embodiments, the allocated time-domain resource is used totransmit or receive the wireless signal.

There are, proposed herein, various embodiments which address one ormore of the issues disclosed herein. Certain embodiments may provide oneor more of the following technical advantage(s). Certain embodimentsallow for more flexible scheduling of time-domain resources withoutincreasing the number of DCI bits.

BRIEF DESCRIPTION OF THE DRAWINGS

FIG. 1 illustrates an example of multiple time-domain resourceallocation tables, in accordance with certain embodiments.

FIG. 2 illustrates an example of a method for use in a wireless device,in accordance with certain embodiments.

FIG. 3 illustrates an example of a method for use in a wireless device,in accordance with certain embodiments.

FIG. 4 illustrates an example of a method for use in a network node, inaccordance with certain embodiments.

FIG. 5 illustrates a schematic block diagram of an apparatus in awireless network, in accordance with certain embodiments.

FIG. 6 illustrates an example of a wireless network, in accordance withsome embodiments.

FIG. 7 illustrates an example of a User Equipment, in accordance withsome embodiments.

FIG. 8 illustrates an example of a virtualization environment, inaccordance with some embodiments.

FIG. 9 illustrates an example of a telecommunication network connectedvia an intermediate network to a host computer, in accordance with someembodiments.

FIG. 10 illustrates an example of a host computer communicating via abase station with a user equipment over a partially wireless connection,in accordance with some embodiments.

FIG. 11 illustrates an example of methods implemented in a communicationsystem including a host computer, a base station and a user equipment,in accordance with some embodiments.

FIG. 12 illustrates an example of methods implemented in a communicationsystem including a host computer, a base station and a user equipment,in accordance with some embodiments.

FIG. 13 illustrates an example of methods implemented in a communicationsystem including a host computer, a base station and a user equipment,in accordance with some embodiments.

FIG. 14 illustrates an example of methods implemented in a communicationsystem including a host computer, a base station and a user equipment,in accordance with some embodiments.

DETAILED DESCRIPTION

Generally, all terms used herein are to be interpreted according totheir ordinary meaning in the relevant technical field, unless adifferent meaning is clearly given and/or is implied from the context inwhich it is used. All references to a/an/the element, apparatus,component, means, step, etc. are to be interpreted openly as referringto at least one instance of the element, apparatus, component, means,step, etc., unless explicitly stated otherwise. The steps of any methodsdisclosed herein do not have to be performed in the exact orderdisclosed, unless a step is explicitly described as following orpreceding another step and/or where it is implicit that a step mustfollow or precede another step. Any feature of any of the embodimentsdisclosed herein may be applied to any other embodiment, whereverappropriate. Likewise, any advantage of any of the embodiments may applyto any other embodiments, and vice versa. Other objectives, features andadvantages of the enclosed embodiments will be apparent from thefollowing description.

Some of the embodiments contemplated herein will now be described morefully with reference to the accompanying drawings. Other embodiments,however, are contained within the scope of the subject matter disclosedherein, the disclosed subject matter should not be construed as limitedto only the embodiments set forth herein; rather, these embodiments areprovided by way of example to convey the scope of the subject matter tothose skilled in the art. Additional information may also be found inAppendix A and Appendix B.

FIG. 1 shows a wireless device configured with multiple (in the example,two) time-domain resource allocation tables. Examples of time-domainresource allocation tables include pre-defined tables with defaultvalues for the time domain resource allocation, tables configured usingRRC signaling, and a combination of pre-defined and RRC-configuredtables. The time-domain resource allocation tables indicate anallocation of time-domain resources, such as time-domain resources ofthe PUSCH or PDSCH, for transmission or reception of a wireless signal.In some embodiments, the time-domain resource allocation tables indicatethe allocation of time-domain resources with reference to OFDM symbols.For example, FIG. 1 shows that the time-domain resource allocationtables comprise different combinations of starting OFDM symbol positionand duration in OFDM symbols for the time-domain resource allocation. Ascan be seen, the time-domain resource allocation tables include multipleentries, and the different table entries may differ in at least one ofOFDM starting symbol and/or scheduled time duration in OFDM symbols. TheOFDM symbols may be indicated using any two parameters selected fromstart symbol, stop symbol, and duration in symbols (e.g., start symboland stop symbol, start symbol and duration, or stop symbol andduration). The start symbol can be absolute with respect to the slotboundary, or relative to a scheduling DCI/CORESET. Different tablescould also have different definitions with respect to the starting (orending) OFDM symbol. For example, some tables could express the starting(or ending) OFDM symbol in absolute OFDM symbol number of a slot whileother tables would express the starting (or ending) symbol relative toPDCCH/CORESET symbol(s) used to schedule PDSCH/PUSCH. The absolutenumbering could be useful for slot-based or Type A transmission whilerelative numbering could be preferred by non-slot-based or Type Btransmission. In principle, different tables could have different numberof entries; however, in the examples shown in FIG. 1 , the same numberof entries in each table is assumed.

The wireless device determines which time-domain resource allocationtable to use based on first information received from a network node,such as a base station. The wireless device determines a time-domainresource allocated to the wireless device based on the time-domainresource allocation table determined from the first information andbased on second information received from the network node. The secondinformation is different from the first information. In someembodiments, the second information indicates which entry of thedetermined table to use to determine the time-domain resource allocatedto the wireless device. For example, the second information may comprisea time-domain resource allocation field, such as a bit field, receivedin DCI. With respect to the example illustrated in FIG. 1 , each tableincludes four entries such that a time-domain resource allocation fieldcomprising a two bits-wide bit field may be used to select one of thefour entries in the table (e.g., value “00” to select the first entry,“01” to select the second entry, “10” to select the third entry, and“11” to select the fourth entry).

As described above, the wireless device determines the table based onfirst information. The first information comprises information otherthan the time-domain resource allocation field received in the DCI.Examples of this other information could be a Radio Network TemporaryIdentifier (RNTI), information contained in the DCI, which DCI formathas been used for scheduling, which CORESET/search space has been usedfor scheduling, if the transmission is slot-based or non-slot-based,carrier aggregation related information, bandwidth part relatedinformation, slot format, and/or information indicating numerology(e.g., a cyclic prefix, an OFDM subcarrier spacing, etc.), as furtherdescribed below.

In some embodiments, the first information could be another field in theDCI (i.e., a field other than the time-domain resource allocation field)that is already being signaled for another purpose. For example, if DCIincludes a bit to differentiate Type A scheduling and Type B scheduling,this bit can be used to select one of the two tables in FIG. 1 . Anotherexample could be a bit that differentiates slot-based transmissions andnon-slot-based transmission. Slot B scheduling, non-slot-basedtransmissions, and mini-slots are transmissions which duration istypically short. Slot-based transmissions typically have transmissionlengths in the order of a slot. Therefore, it makes sense to use twodifferent time-domain resource allocation tables based on a Type A/TypeB or non-slot-based-transmission/slot-based-transmission differentiatorbit.

If multi-slot scheduling is dynamically indicated in the DCI using amulti-slot indicator bit, this bit can be used as the first informationto differentiate a time-domain resource allocation table to be used forsingle slot and multi-slot (slot aggregation) transmission. In these twocases resource allocations are obviously different. A multi-slottime-domain resource allocation can—in addition to the symbolinformation—also contain slot information. Here the time-domain resourceallocation field received in DCI could be larger bit field if themulti-slot indicator bit is set to enable more time-domain resourceallocations. The same principle applies if multi-slot scheduling is notindicated via a multi-slot indicator bit in the DCI but in any otherway.

Certain embodiments of the present disclosure use the DCI format (e.g.,regular DCI or fallback DCI) as the first information for selecting atime-domain resource allocation table. For example, for NR, it has beendiscussed in 3GPP to use two different DCI variants. The first variantis a regular DCI which can be used for all kinds of signaling orconfiguring needed. This regular DCI varies in size and format dependingon its use (i.e., depending on the actual RRC configuration), somewhatsimilar to LTE DCI formats. The second variant is a fallback DCI with afixed and predefined size. The fixed-size fallback DCI is typicallyneeded during RRC reconfigurations, when there may be a period ofconfiguration uncertainty during which it is valuable to have a fixedsized DCI known to both the network and the UE, to limit the effect ofthe configuration uncertainty for the wireless communication. Theproblem of configuration uncertainty occurs when the network does notknow when the UE applies the RRC reconfiguration. For example, the UEmay have to list the information, or there may be multipleretransmissions needed before the RRC command reaches the UE. Hencethere is a period when the UE may have applied the new configuration,but the network is not aware of it, or vice versa. During this periodthere is thus a need for a way to communicate which is “always” known byboth sides and, and this need is fulfilled by using the fallback DCIthat is not configurable.

A wireless device can be configured with multiple control channelresource sets (CORESETS) and each CORESET can contain one or more searchspaces. The CORESET and/or search space that has been used to schedulethe transmission can be used as the first information for determiningthe time-domain resource allocation table.

A DCI contains a downlink/uplink (DL/UL) indicator bit that indicates ifthe transmission is DL or UL. Due to the difference in frame structureand different processing times between DL assignment reception→DL datareception and UL grant reception→UL data transmission, it is likely thatDL and UL require different time-domain resource allocations. Therefore,the DL/UL indicator bit can be used as the first information fordetermining the time-domain resource allocation table.

In case of carrier aggregation, a wireless device is configured withmultiple carriers. Different carriers might have different numerologies,and different need to coexist with long term evolution (LTE), and areset up with different DL/UL configurations. Then it makes sense tosupport different time-domain resource allocations for differentcarriers. Therefore, depending on the scheduled carrier, a time-domainresource allocation table is selected (i.e., the scheduled carrier maybe used as first information for determining the time-domain resourceallocation table). If no cross-carrier scheduling is applied (i.e.,PDCCH is transmitted on same carrier as PDSCH or on associated carrierto PUSCH carrier) the carrier on which the scheduling DCI is transmitteddetermines the time-domain resource allocation table. If cross carrierscheduling is used (i.e., PDCCH is transmitted on another carrier asPDSCH or associated carrier to PUSCH carrier), information in the DCI orhow the DCI is transmitted indicates the PDSCH/PUSCH carrier. Forexample, a Carrier Indicator Field (CIF) can be included in the DCIpointing to the PDSCH/PUSCH carrier. Different offsets with respect tohow a search space is located in a CORESET might also be used toindicate the PDSCH/PUSCH carrier. Based on the identified carrier, atime-domain resource allocation table is selected.

In LTE and NR, transmissions can be scheduled using different RadioNetwork Temporary Identifiers (RNTI). As the name implies, RNTI is akind of identification number, used to identify a specific radio channeland sometimes also a specific UE. Some examples are:

C-RNTI: used for scheduling at cell level. C-RNTI is a unique UE id usedas an identifier of the RRC Connection and for scheduling.

RA-RNTI used during random access procedure.

SI-RNTI: identification of System Information in the downlink.

P-RNTI: identification of Paging and System Information changenotification in the downlink.

For example, it could be envisioned that different RNTIs are used toschedule slot-based transmission and non-slot-based transmissions.Different RNTIs can therefore be mapped to different time-domainresource allocation and the wireless device—depending on which RNTI itdetects—selects a time-domain resource allocation table. Thus, an RNTImay be used as first information for determining the time-domainresource allocation table.

NR supports different numerologies, e.g., OFDM subcarrier spacing and/orcyclic prefix. Different numerologies (including cyclic prefix) can beused to optimize transmissions with respect to latency or individuallyadopt the numerology to the current radio conditions of a terminal.Different numerologies can be mapped to different time-domain resourceallocation and the wireless device, based on the numerology of atransmission, selects the correct time-domain resource allocation table.In NR, different bandwidth parts (BWP) will be used for differentnumerologies. Different BWP might thus use different time-domainresource allocation tables. For example, if the DCI contains a BWPindicator field this can be used as first information for determiningthe time-domain resource allocation table.

Yet another possibility is to use the slot format as first informationfor determining the time-domain resource allocation table. For example,the wireless device can determine which table to use based on a slotformat determined by the wireless device. The slot format can bedetermined based on the slot in which PDSCH is received (or PUSCH istransmitted). Alternately the slot format can be determined based on theformat applicable to the first slot from which the PDSCH is received (orPUSCH is transmitted) in case of multi-slot transmissions. The slotformat can be determined by the wireless device via higher layersignaling and/or L1 signaling (e.g., slot format indicator received inDCI or group-common PDCCH) and indicates at least one more ofdownlink/uplink/unknown symbols within a slot.

In initial access, Remaining Minimum System Information (RMSI) can betransmitted based on slot-based transmissions and non-slot-basedtransmissions. The Master Information Block (MIB) on the PhysicalBroadcast Channel (PBCH) contain information about how RMSI isdistributed. Depending on how RMSI is transmitted, different time-domainresource allocation tables can be used to maximize schedulingflexibility for RMSI. Thus, information related to how the RMSI istransmitted may be used as first information for determining the timedomain resource allocation table.

FIG. 2 shows a flow chart of a method in a wireless device for how toselect a time-domain resource allocation table and a time-domainresource allocation entry within the table. First, the method comprisesselecting a time-domain resource allocation table. In some embodiments,the method comprises selecting one of multiple time-domain resourceallocation tables based on information available to the network node andthe wireless device, for example, without the network node having tosend DCI explicitly indicating which time-domain resource allocationtable the wireless device should select. Second, the method comprisesdetermining a time-domain resource allocation entry within the selectedtable. For example, from the network node perspective, the network nodedetermines the time-domain resource allocation entry and explicitlysignals the entry in the time-domain resource allocation field in DCI.From the wireless device perspective, the wireless device determines thetime-domain resource allocation entry within the selected table based onthe time-domain resource allocation field received in DCI from thenetwork node.

In addition, it is possible that the tables discussed above areconfigured from a set of possible time-domain resource allocations. Anexample of a collection of time-domain resource allocations is givenbelow in Table 1.

TABLE 1 Possible time-domain resource allocations (captured in spec)Time domain PDSCH start offset from RA last OFDM symbol of Index PDCCHPDSCH Applicable slots (I_TDRA) (X syms) length (L1 syms) (L2 slots)Comments  0-13 0 1-14 1 1^(st) index corresponds to L1 = 1; 2^(nd) indexto L1 = 2, . . .  14-24 1 1-13 1 1^(st) index corresponds to L1 = 1;2^(nd) index to L1 = 2, . . .  25-36 2 1-12 1 1^(st) index correspondsto L1 = 1; 2^(nd) index to L1 = 2, . . .  37-48 3 1-11 1 1^(st) indexcorresponds to L1 = 1; 2^(nd) index to L1 = 2, . . .  49-59 4 1-10 1 60-72 −1 3-14 1 1^(st) index corresponds to L1 = 1; 2^(nd) index to L1= 2, . . .  73-84 −2 4-14 1 1^(st) index corresponds to L1 = 1; 2^(nd)index to L1 = 2, . . .  85-91 0 14 2-8 1^(st) index corresponds to L2 =1; 2^(nd) index to L2 = 2, . . .  92-98 0 13 2-8 1^(st) indexcorresponds to L2 = 1; 2^(nd) index to L2 = 2, . . .  99-105 0 12 2-81^(st) index corresponds to L2 = 1; 2^(nd) index to L2 = 2, . . .106-112 0 11 2-8 1^(st) index corresponds to L2 = 1; 2^(nd) index to L2= 2, . . . 113-119 1 13 2-8 1^(st) index corresponds to L2 = 1; 2^(nd)index to L2 = 2, . . . 120-126 1 12 2-8 1^(st) index corresponds to L2 =1; 2^(nd) index to L2 = 2, . . . 127-133 1 11 2-8 1^(st) indexcorresponds to L2 = 1; 2^(nd) index to L2 = 2, . . . 134-140 2 12 2-81^(st) index corresponds to L2 = 1; 2^(nd) index to L2 = 2, . . .141-147 2 11 2-8 1^(st) index corresponds to L2 = 1; 2^(nd) index to L2= 2, . . . 148-155 3 11 2-8 1^(st) index corresponds to L2 = 1; 2^(nd)index to L2 = 2, . . . 156-163 All DL symbols determined from the SFI ofthe slot in 1-8 1^(st) index which PDSCH is received corresponds to L2 =1; 2^(nd) index to L2 = 2, . . . 164 All DL symbols determined from theSFI of the slot in 1 which PDSCH is received; starting from the lastOFDM symbol in which PDCCH is received other values reserved (e.g., upto 255)

In Table 1, the multi-slot scheduling has been directly included as aseparate column in the table. It is found under the column “Applicableslots (L2 slots).” In other embodiments, the multi-slot scheduling maybe indicated by other means. In some embodiments, four entries of Table1 could be configured to build Table A of FIG. 1 (e.g., Table A has fourentries in the example shown in FIG. 1 ). The signaling for this can bein system information or by wireless device-specific signaling by radioresource control (RRC). Similar methods can also be done for Table B andso on.

A table would then be selected according first information, such as anRNTI, information contained in the DCI, which DCI format has been usedfor scheduling, which CORESET/search space has been used for scheduling,if the transmission is slot-based or non-slot-based, carrier aggregationrelated information, bandwidth part related information, slot format,and/or information indicating numerology (e.g., a cyclic prefix, an OFDMsubcarrier spacing, etc.). The time-domain resource allocation field inthe DCI will point out an entry in the selected table. It is furtherobserved that although Table 1 is described for PDSCH, a similar tablecan be constructed for PUSCH. As said earlier, different tables (TableA, Table B, . . . ) can be configured for different CORESET/searchspaces/ . . . , and each Table A, B, . . . is configured with rows fromTable 1.

Specific for initial access, some entries for Table 1 can be directlyhardcoded in the specification for scheduling of example systeminformation, paging, random access response, Message 3 in the randomaccess procedure. If there would be no default values, additionalsignaling would be needed in MIB/PBCH to configure the defaulttime-domain resource allocation(s). These values can also be defaultvalues the wireless device uses unless configured with a new time-domainresource allocation table.

Any appropriate steps, methods, features, functions, or benefitsdisclosed herein may be performed through one or more functional unitsor modules of one or more virtual apparatuses. Each virtual apparatusmay comprise a number of these functional units. These functional unitsmay be implemented via processing circuitry, which may include one ormore microprocessor or microcontrollers, as well as other digitalhardware, which may include digital signal processors (DSPs),special-purpose digital logic, and the like. The processing circuitrymay be configured to execute program code stored in memory, which mayinclude one or several types of memory such as read-only memory (ROM),random-access memory (RAM), cache memory, flash memory devices, opticalstorage devices, etc. Program code stored in memory includes programinstructions for executing one or more telecommunications and/or datacommunications protocols as well as instructions for carrying out one ormore of the techniques described herein. In some implementations, theprocessing circuitry may be used to cause the respective functional unitto perform corresponding functions according one or more embodiments ofthe present disclosure.

FIG. 3 depicts a method in accordance with particular embodiments. Incertain embodiments, the method may be performed by a wireless device,such as a UE. The method begins at step 30 with determining one of aplurality of time-domain resource allocation tables based on firstinformation received from a network node. The method continues to step32 with determining a time-domain resource allocated to the wirelessdevice for transmission or reception of a wireless signal based on thedetermined one of the plurality of time-domain resource allocationtables and second information received from the network node differentfrom the first information. Examples of first information, i.e.,information from which the wireless device may determine the time-domainresource allocation table and second information, i.e., information fromwhich the wireless device may determine the time-domain resourceinclude, but are not limited to, the examples described with respect toFIGS. 1-2 and above and the Group A embodiments below. In someembodiments, the method further comprises transmitting or receiving thewireless signal at step 34 using the determined time-domain resource.

FIG. 4 depicts a method in accordance with particular embodiments. Incertain embodiments, the method may be performed by a network node, suchas a base station. The method begins at step 40 with determining atime-domain resource to allocate to a wireless device for transmissionor reception of a wireless signal. For example, in some embodiments, thenetwork node determines the time-domain resource allocation based on anidentified table and other information, such as current schedulingneeds. The network node may then select the entry from the table thatcorresponds to the determined time-domain resource allocation.Additionally, the network node may determine second information forindicating the selected entry to the wireless device. The methodproceeds to step 42 with sending the wireless device first informationfrom which the wireless device determines one of a plurality oftime-domain resource allocation tables and second information from whichthe wireless device determines the time-domain resource based on thedetermined one of the plurality of time-domain resource allocationtables. The second information is different from the first information.Examples of first information, i.e., information sent to the wirelessdevice from which the wireless device may determine the time-domainresource allocation table and second information, i.e., information sentto the wireless device from which the wireless device may determine thetime-domain resource include, but are not limited to, the examplesdescribed with respect to FIGS. 1-2 and above and the Group Bembodiments below. In some embodiments, the method further comprisestransmitting or receiving the wireless signal at step 44 using theallocated time-domain resource.

With respect to the examples in FIGS. 3 and 4 , in certain embodiments,the first information comprises one or more of:

a. information contained in downlink control information (DCI) from thenetwork and signalled to the wireless device for another purpose besidesdetermining the time-domain resource;

b. information indicating which DCI format has been used for scheduling(e.g., regular DCI format or fallback DCI format);

c. information indicating which CORESET/search space has been used forscheduling;

d. information indicating if the transmission is slot-based ornon-slot-based;

e. carrier aggregation related information;

f. bandwidth part related information;

g. information indicating a slot format;

h. information indicating if the transmission is single slot ormulti-slot;

i. configuration of downlink/uplink indicator received in DCI;

j. Radio Network Temporary Identifiers (RNTI); and/or

k. information indicating numerology (e.g., OFDM subcarrier spacingand/or cyclic prefix).

The second information comprises a time-domain resource allocation fieldwithin downlink control information that allows the wireless device/UEto determine which entry to use within the determined one of theplurality of tables in order to determine the allocated time-domainresource.

FIG. 5 illustrates a schematic block diagram of an apparatus 50 in awireless network (for example, the wireless network shown in FIG. 6 ).The apparatus may be implemented in a wireless device or network node(e.g., wireless device 110 or network node 160 shown in FIG. 6 ).Apparatus 50 is operable to carry out the example method described withreference to FIG. 3 or FIG. 4 and possibly any other processes ormethods disclosed herein. It is also to be understood that the method ofFIGS. 3 and 4 are not necessarily carried out solely by apparatus 50. Atleast some operations of the method can be performed by one or moreother entities.

Virtual Apparatus 50 may comprise processing circuitry, which mayinclude one or more microprocessor or microcontrollers, as well as otherdigital hardware, which may include digital signal processors (DSPs),special-purpose digital logic, and the like. The processing circuitrymay be configured to execute program code stored in memory, which mayinclude one or several types of memory such as read-only memory (ROM),random-access memory, cache memory, flash memory devices, opticalstorage devices, etc. Program code stored in memory includes programinstructions for executing one or more telecommunications and/or datacommunications protocols as well as instructions for carrying out one ormore of the techniques described herein, in several embodiments. In someimplementations, the processing circuitry may be used to causeconfiguration information unit 52, time resource determination unit 54,communication unit 56, and any other suitable units of apparatus 50 toperform corresponding functions according one or more embodiments of thepresent disclosure.

As illustrated in FIG. 5 , apparatus 50 includes configurationinformation unit 52, time resource determination unit 54, andcommunication unit 56. In certain embodiments, configuration informationunit 52 is configured to determine first information and secondinformation. For example, when used in a network node, configurationinformation unit 52 determines first information to send to a wirelessdevice from which the wireless device determines one of a plurality oftables, and second information from which the wireless determines (basedon the one of the plurality of tables determined from the firstinformation) an allocated time-domain resource. When used in a wirelessdevice, configuration information unit 52 determines the first andsecond information received from the network node. Time resourcedetermination unit 54 determines a time resource allocated to thewireless device for transmission or reception of a wireless signal. Whenused in a network node, time resource determination unit 54 may allocatea time-domain resource and may indicate the allocated time-domainresource to the network node's configuration information unit 52 so thatthe configuration information unit 52 can determine the first and secondinformation to send the wireless device (e.g., first and secondinformation that corresponds to the allocated time-domain resource).When used in a wireless device, time resource determination unit 54 canreceive the first and second information from the network node (e.g.,via the wireless device's configuration information module 52) and canuse the first and second information to determine the time-domainresource that the network node has allocated for the transmission orreception of a wireless signal. Communication unit 56 transmits orreceives the wireless signal according to the allocated time domainresource that was determined by the time resource determination unit 54.

The term unit may have conventional meaning in the field of electronics,electrical devices and/or electronic devices and may include, forexample, electrical and/or electronic circuitry, devices, modules,processors, memories, logic solid state and/or discrete devices,computer programs or instructions for carrying out respective tasks,procedures, computations, outputs, and/or displaying functions, and soon, as such as those that are described herein.

In some embodiments a computer program, computer program product orcomputer readable storage medium comprises instructions which whenexecuted on a computer perform any of the embodiments disclosed herein.In further examples the instructions are carried on a signal or carrierand which are executable on a computer wherein when executed perform anyof the embodiments disclosed herein.

Embodiments Group A Embodiments

-   -   1. A method performed by a wireless device, the method        comprising:        -   determining one of a plurality of tables based on first            information received from a network node (e.g., base            station),        -   determining a time-domain resource allocated to the wireless            device for transmission or reception of a wireless signal            based on the determined one of the plurality of tables and            second information received from the network node different            from or other than the first information.    -   2. The method of the previous embodiment, wherein the plurality        of tables are time-domain resource allocation tables.    -   3. The method of any of the previous embodiments, further        comprising transmitting or receiving the wireless signal using        the determined time-domain resource.    -   4. The method of any of the previous embodiments, wherein the        second information is a time-domain resource allocation field        received in downlink control information.    -   5. The method of any of the previous embodiments, wherein the        first information comprises one or more of:        -   a. information contained in downlink control            information (DCI) from the network and signalled to the            wireless device for another purpose besides determining the            time-domain resource;        -   b. information indicating which DCI format has been used for            scheduling (e.g., regular DCI format or fallback DCI            format);        -   c. information indicating which CORESET/search space has            been used for scheduling;        -   d. information indicating if the transmission is slot-based            or non-slot-based;        -   e. carrier aggregation related information;        -   f. bandwidth part related information;        -   g. information indicating a slot format;        -   h. information indicating if the transmission is single slot            or multi-slot;        -   i. configuration of downlink/uplink indicator received in            DCI;        -   j. Radio Network Temporary Identifiers (RNTI); and/or        -   k. information indicating numerology (e.g., OFDM subcarrier            spacing and/or cyclic prefix).    -   6. A method performed by a wireless device, the method        comprising:        -   using a selected one of a plurality of tables to determine a            time-domain resource that a network has allocated to the            wireless device for transmission or reception of a wireless            signal.    -   7. The method of the previous embodiment, further comprising        determining the selected table based on information other than a        time-domain resource allocation field received in downlink        control information from the network.

-   8. The method of any of the previous embodiments, further comprising    making the selection of the selected table at the wireless device    based on information that is available to both the network and the    wireless device.    -   9. The method of example embodiment 6, wherein the information        used to make the selection of the selected table comprises one        or more of:        -   information contained in downlink control information (DCI)            from the network and signalled to the wireless device for            another purpose besides identifying the selected time-domain            resource allocation;        -   which DCI format has been used for scheduling (e.g., regular            DCI format or fallback DCI format);        -   which CORESET/search space has been used for scheduling;        -   if the transmission is slot-based or non-slot-based;        -   carrier aggregation related information;        -   bandwidth part related information;        -   slot format;        -   if the transmission is single slot or multi-slot;        -   configuration of downlink/uplink indicator received in DCI;        -   Radio Network Temporary Identifiers (RNTI); and/or        -   numerology (e.g., OFDM subcarrier spacing and/or cyclic            prefix).    -   10. The method of any of the previous embodiments, wherein when        the time-domain resource allocation is used in scheduling system        information, the selected table is based on whether the system        information is distributed according to slot-based or non-slot        based transmission.    -   11. The method of any of the previous embodiments, further        comprising determining a selected one of a plurality of entries        within the selected table, the selected entry indicating the        time-domain resource that the network has allocated to the        wireless device for the transmission or reception of the        wireless signal.    -   12. The method of the previous embodiment, wherein the selected        entry is determined based on an explicit indication received        from the network.    -   13. The method of the previous embodiment, wherein the explicit        indication is received via a time-domain resource allocation bit        field received in downlink control information from the network.    -   14. The method of any of the previous embodiments, wherein the        selected entry indicates at least two of a start symbol, a stop        symbol, and a duration in symbols for the transmission or        reception of the wireless signal.    -   15. The method of any of the previous embodiments, further        comprising transmitting the wireless signal on a physical uplink        shared channel (PUSCH) using the allocated time-domain resource.    -   16. The method of any of the previous embodiments, further        comprising receiving the wireless signal on a physical downlink        shared channel (PDSCH) using the allocated time-domain resource.    -   17. The method of any of the previous embodiments, wherein:        -   a first of the plurality of tables expresses a start or end            OFDM symbol as an absolute OFDM symbol number relative to a            slot boundary, and        -   a second of the plurality of tables expresses the start or            end OFDM symbol relative to PDCCH/CORESET symbol(s) used to            schedule PDSCH/PUSCH.    -   18. The method of any of the previous embodiments, wherein a        first of the plurality of tables comprises a different number of        entries than a second of the plurality of tables.    -   19. The method of any of the previous embodiments, wherein each        of the plurality of tables comprises the same number of entries.    -   20. The method of any of the previous embodiments, further        comprising:        -   providing user data; and        -   forwarding the user data to a host computer via the            transmission to the network node.

Group B Embodiments

-   -   21. A method performed by a base station, the method comprising:        -   determining a time-domain resource to allocate to a wireless            device for transmission or reception of a wireless signal,            and        -   sending the wireless device first information from which the            wireless device determines one of a plurality of tables and            second information from which the wireless determines, based            on the one of the plurality of tables, the allocated            time-domain resource, the second information different from            or other than the first information.    -   22. The method of the previous embodiment, wherein the plurality        of tables are time-domain resource allocation tables.    -   23. The method of any of the previous embodiments, further        comprising transmitting or receiving the wireless signal using        the determined time-domain resource.    -   24. The method of any of the previous embodiments, wherein the        second information is a time-domain resource allocation field        sent in downlink control information.    -   25. The method of any of the previous embodiments, wherein the        first information comprises one or more of:        -   a. information contained in downlink control            information (DCI) signaled from the base station to the            wireless device for another purpose besides determining the            time-domain resource;        -   b. information indicating which DCI format has been used for            scheduling (e.g., regular DCI format or fallback DCI            format);        -   c. information indicating which CORESET/search space has            been used for scheduling;        -   d. information indicating if the transmission is slot-based            or non-slot-based;        -   e. carrier aggregation related information;        -   f. bandwidth part related information;        -   g. information indicating a slot format;        -   h. information indicating if the transmission is single slot            or multi-slot;        -   i. configuration of downlink/uplink indicator received in            DCI;        -   j. Radio Network Temporary Identifiers (RNTI); and/or        -   k. information indicating numerology (e.g., OFDM subcarrier            spacing and/or cyclic prefix).    -   26. A method performed by a network node (e.g., base station),        the method comprising:        -   determining one of a plurality of tables that a wireless            device is using to determine which time-domain resource the            network node is allocating to the wireless device for            transmission or reception of a wireless signal;        -   sending the wireless device information indicating one of a            plurality of entries within the determined one of the            plurality of tables, the selected entry indicating a            time-domain resource that has been allocated to the wireless            device for the transmission or reception of the wireless            signal.    -   27. The method of any of the previous embodiments, wherein the        one of the plurality of tables is determined based on        information that is available to both the network node and the        wireless device.    -   28. The method of example embodiment 26, wherein the information        used to determine which table the wireless device is using        (i.e., the one of the plurality of tables) comprises:        -   information contained in downlink control information (DCI)            that the network signals to the wireless device for another            purpose besides identifying the selected time-domain            resource allocation;        -   which DCI format has been used for scheduling (e.g., regular            DCI format or fallback DCI format);        -   which CORESET/search space has been used for scheduling;        -   if the transmission is slot-based or non-slot-based;        -   carrier aggregation related information;        -   bandwidth part related information;        -   slot format;        -   if the transmission is single slot or multi-slot;        -   configuration of downlink/uplink indicator received in DCI;        -   Radio Network Temporary Identifiers (RNTI); and/or        -   numerology (e.g., OFDM subcarrier spacing and/or cyclic            prefix).    -   29. The method of any of the previous embodiments, wherein when        the time-domain resource allocation is used in scheduling system        information, the one of the plurality of tables is determined        based on whether the system information is distributed according        to slot-based or non-slot based transmission.    -   30. The method of the previous embodiment, wherein the        information indicating the one of the plurality of entries is        sent explicitly.    -   31. The method of the previous embodiment, wherein the        information indicating the one of the plurality of entries is        sent via a time-domain resource allocation bit field in downlink        control information sent to the wireless device.    -   32. The method of any of the previous embodiments, wherein the        one of the plurality of entries indicates at least two of a        start symbol, a stop symbol, and a duration in symbols for the        transmission or reception of the wireless signal.    -   33. The method of any of the previous embodiments, further        comprising receiving the wireless signal on a physical uplink        shared channel (PUSCH) using the allocated time-domain resource.    -   34. The method of any of the previous embodiments, further        comprising transmitting the wireless signal on a physical        downlink shared channel (PDSCH) using the allocated time-domain        resource.    -   35. The method of any of the previous embodiments, wherein:        -   a first of the plurality of tables expresses a start or end            OFDM symbol as an absolute OFDM symbol number relative to a            slot boundary, and        -   a second of the plurality of tables expresses the start or            end OFDM symbol relative to PDCCH/CORESET symbol(s) used to            schedule PDSCH/PUSCH.    -   36. The method of any of the previous embodiments, wherein a        first of the plurality of tables comprises a different number of        entries than a second of the plurality of tables.    -   37. The method of any of the previous embodiments, wherein each        of the plurality of tables comprises the same number of entries.    -   38. The method of any of the previous embodiments, further        comprising:        -   obtaining user data; and        -   forwarding the user data to a host computer or a wireless            device.

Although the subject matter described herein may be implemented in anyappropriate type of system using any suitable components, theembodiments disclosed herein are described in relation to a wirelessnetwork, such as the example wireless network illustrated in FIG. 6 .For simplicity, the wireless network of FIG. 6 only depicts network 106,network nodes 160 and 160 b, and WDs 110, 110 b, and 110 c. In practice,a wireless network may further include any additional elements suitableto support communication between wireless devices or between a wirelessdevice and another communication device, such as a landline telephone, aservice provider, or any other network node or end device. Of theillustrated components, network node 160 and wireless device (WD) 110are depicted with additional detail. The wireless network may providecommunication and other types of services to one or more wirelessdevices to facilitate the wireless devices' access to and/or use of theservices provided by, or via, the wireless network.

The wireless network may comprise and/or interface with any type ofcommunication, telecommunication, data, cellular, and/or radio networkor other similar type of system. In some embodiments, the wirelessnetwork may be configured to operate according to specific standards orother types of predefined rules or procedures. Thus, particularembodiments of the wireless network may implement communicationstandards, such as Global System for Mobile Communications (GSM),Universal Mobile Telecommunications System (UMTS), Long Term Evolution(LTE), and/or other suitable 2G, 3G, 4G, or 5G standards; wireless localarea network (WLAN) standards, such as the IEEE 802.11 standards; and/orany other appropriate wireless communication standard, such as theWorldwide Interoperability for Microwave Access (WiMax), Bluetooth,Z-Wave and/or ZigBee standards.

Network 106 may comprise one or more backhaul networks, core networks,IP networks, public switched telephone networks (PSTNs), packet datanetworks, optical networks, wide-area networks (WANs), local areanetworks (LANs), wireless local area networks (WLANs), wired networks,wireless networks, metropolitan area networks, and other networks toenable communication between devices.

Network node 160 and WD 110 comprise various components described inmore detail below. These components work together in order to providenetwork node and/or wireless device functionality, such as providingwireless connections in a wireless network. In different embodiments,the wireless network may comprise any number of wired or wirelessnetworks, network nodes, base stations, controllers, wireless devices,relay stations, and/or any other components or systems that mayfacilitate or participate in the communication of data and/or signalswhether via wired or wireless connections.

As used herein, network node refers to equipment capable, configured,arranged and/or operable to communicate directly or indirectly with awireless device and/or with other network nodes or equipment in thewireless network to enable and/or provide wireless access to thewireless device and/or to perform other functions (e.g., administration)in the wireless network. Examples of network nodes include, but are notlimited to, access points (APs) (e.g., radio access points), basestations (BSs) (e.g., radio base stations, Node Bs, evolved Node Bs(eNBs) and NR NodeBs (gNBs)). Base stations may be categorized based onthe amount of coverage they provide (or, stated differently, theirtransmit power level) and may then also be referred to as femto basestations, pico base stations, micro base stations, or macro basestations. A base station may be a relay node or a relay donor nodecontrolling a relay. A network node may also include one or more (orall) parts of a distributed radio base station such as centralizeddigital units and/or remote radio units (RRUs), sometimes referred to asRemote Radio Heads (RRHs). Such remote radio units may or may not beintegrated with an antenna as an antenna integrated radio. Parts of adistributed radio base station may also be referred to as nodes in adistributed antenna system (DAS). Yet further examples of network nodesinclude multi-standard radio (MSR) equipment such as MSR BSs, networkcontrollers such as radio network controllers (RNCs) or base stationcontrollers (BSCs), base transceiver stations (BTSs), transmissionpoints, transmission nodes, multi-cell/multicast coordination entities(MCEs), core network nodes (e.g., MSCs, MMEs), O&M nodes, OSS nodes, SONnodes, positioning nodes (e.g., E-SMLCs), and/or MDTs. As anotherexample, a network node may be a virtual network node as described inmore detail below. More generally, however, network nodes may representany suitable device (or group of devices) capable, configured, arranged,and/or operable to enable and/or provide a wireless device with accessto the wireless network or to provide some service to a wireless devicethat has accessed the wireless network.

In FIG. 6 , network node 160 includes processing circuitry 170, devicereadable medium 180, interface 190, auxiliary equipment 184, powersource 186, power circuitry 187, and antenna 162. Although network node160 illustrated in the example wireless network of FIG. 6 may representa device that includes the illustrated combination of hardwarecomponents, other embodiments may comprise network nodes with differentcombinations of components. It is to be understood that a network nodecomprises any suitable combination of hardware and/or software needed toperform the tasks, features, functions and methods disclosed herein.Moreover, while the components of network node 160 are depicted assingle boxes located within a larger box, or nested within multipleboxes, in practice, a network node may comprise multiple differentphysical components that make up a single illustrated component (e.g.,device readable medium 180 may comprise multiple separate hard drives aswell as multiple RAM modules).

Similarly, network node 160 may be composed of multiple physicallyseparate components (e.g., a NodeB component and a RNC component, or aBTS component and a BSC component, etc.), which may each have their ownrespective components. In certain scenarios in which network node 160comprises multiple separate components (e.g., BTS and BSC components),one or more of the separate components may be shared among severalnetwork nodes. For example, a single RNC may control multiple NodeB's.In such a scenario, each unique NodeB and RNC pair, may in someinstances be considered a single separate network node. In someembodiments, network node 160 may be configured to support multipleradio access technologies (RATs). In such embodiments, some componentsmay be duplicated (e.g., separate device readable medium 180 for thedifferent RATs) and some components may be reused (e.g., the sameantenna 162 may be shared by the RATs). Network node 160 may alsoinclude multiple sets of the various illustrated components fordifferent wireless technologies integrated into network node 160, suchas, for example, GSM, WCDMA, LTE, NR, WiFi, or Bluetooth wirelesstechnologies. These wireless technologies may be integrated into thesame or different chip or set of chips and other components withinnetwork node 160.

Processing circuitry 170 is configured to perform any determining,calculating, or similar operations (e.g., certain obtaining operations)described herein as being provided by a network node. These operationsperformed by processing circuitry 170 may include processing informationobtained by processing circuitry 170 by, for example, converting theobtained information into other information, comparing the obtainedinformation or converted information to information stored in thenetwork node, and/or performing one or more operations based on theobtained information or converted information, and as a result of saidprocessing making a determination.

Processing circuitry 170 may comprise a combination of one or more of amicroprocessor, controller, microcontroller, central processing unit,digital signal processor, application-specific integrated circuit, fieldprogrammable gate array, or any other suitable computing device,resource, or combination of hardware, software and/or encoded logicoperable to provide, either alone or in conjunction with other networknode 160 components, such as device readable medium 180, network node160 functionality. For example, processing circuitry 170 may executeinstructions stored in device readable medium 180 or in memory withinprocessing circuitry 170. Such functionality may include providing anyof the various wireless features, functions, or benefits discussedherein. In some embodiments, processing circuitry 170 may include asystem on a chip (SOC).

In some embodiments, processing circuitry 170 may include one or more ofradio frequency (RF) transceiver circuitry 172 and baseband processingcircuitry 174. In some embodiments, radio frequency (RF) transceivercircuitry 172 and baseband processing circuitry 174 may be on separatechips (or sets of chips), boards, or units, such as radio units anddigital units. In alternative embodiments, part or all of RF transceivercircuitry 172 and baseband processing circuitry 174 may be on the samechip or set of chips, boards, or units

In certain embodiments, some or all of the functionality describedherein as being provided by a network node, base station, eNB or othersuch network device may be performed by processing circuitry 170executing instructions stored on device readable medium 180 or memorywithin processing circuitry 170. In alternative embodiments, some or allof the functionality may be provided by processing circuitry 170 withoutexecuting instructions stored on a separate or discrete device readablemedium, such as in a hard-wired manner. In any of those embodiments,whether executing instructions stored on a device readable storagemedium or not, processing circuitry 170 can be configured to perform thedescribed functionality. The benefits provided by such functionality arenot limited to processing circuitry 170 alone or to other components ofnetwork node 160, but are enjoyed by network node 160 as a whole, and/orby end users and the wireless network generally.

Device readable medium 180 may comprise any form of volatile ornon-volatile computer readable memory including, without limitation,persistent storage, solid-state memory, remotely mounted memory,magnetic media, optical media, random access memory (RAM), read-onlymemory (ROM), mass storage media (for example, a hard disk), removablestorage media (for example, a flash drive, a Compact Disk (CD) or aDigital Video Disk (DVD)), and/or any other volatile or non-volatile,non-transitory device readable and/or computer-executable memory devicesthat store information, data, and/or instructions that may be used byprocessing circuitry 170. Device readable medium 180 may store anysuitable instructions, data or information, including a computerprogram, software, an application including one or more of logic, rules,code, tables, etc. and/or other instructions capable of being executedby processing circuitry 170 and, utilized by network node 160. Devicereadable medium 180 may be used to store any calculations made byprocessing circuitry 170 and/or any data received via interface 190. Insome embodiments, processing circuitry 170 and device readable medium180 may be considered to be integrated.

Interface 190 is used in the wired or wireless communication ofsignalling and/or data between network node 160, network 106, and/or WDs110. As illustrated, interface 190 comprises port(s)/terminal(s) 194 tosend and receive data, for example to and from network 106 over a wiredconnection. Interface 190 also includes radio front end circuitry 192that may be coupled to, or in certain embodiments a part of, antenna162. Radio front end circuitry 192 comprises filters 198 and amplifiers196. Radio front end circuitry 192 may be connected to antenna 162 andprocessing circuitry 170. Radio front end circuitry may be configured tocondition signals communicated between antenna 162 and processingcircuitry 170. Radio front end circuitry 192 may receive digital datathat is to be sent out to other network nodes or WDs via a wirelessconnection. Radio front end circuitry 192 may convert the digital datainto a radio signal having the appropriate channel and bandwidthparameters using a combination of filters 198 and/or amplifiers 196. Theradio signal may then be transmitted via antenna 162. Similarly, whenreceiving data, antenna 162 may collect radio signals which are thenconverted into digital data by radio front end circuitry 192. Thedigital data may be passed to processing circuitry 170. In otherembodiments, the interface may comprise different components and/ordifferent combinations of components.

In certain alternative embodiments, network node 160 may not includeseparate radio front end circuitry 192, instead, processing circuitry170 may comprise radio front end circuitry and may be connected toantenna 162 without separate radio front end circuitry 192. Similarly,in some embodiments, all or some of RF transceiver circuitry 172 may beconsidered a part of interface 190. In still other embodiments,interface 190 may include one or more ports or terminals 194, radiofront end circuitry 192, and RF transceiver circuitry 172, as part of aradio unit (not shown), and interface 190 may communicate with basebandprocessing circuitry 174, which is part of a digital unit (not shown).

Antenna 162 may include one or more antennas, or antenna arrays,configured to send and/or receive wireless signals. Antenna 162 may becoupled to radio front end circuitry 190 and may be any type of antennacapable of transmitting and receiving data and/or signals wirelessly. Insome embodiments, antenna 162 may comprise one or more omni-directional,sector or panel antennas operable to transmit/receive radio signalsbetween, for example, 2 GHz and 66 GHz. An omni-directional antenna maybe used to transmit/receive radio signals in any direction, a sectorantenna may be used to transmit/receive radio signals from deviceswithin a particular area, and a panel antenna may be a line of sightantenna used to transmit/receive radio signals in a relatively straightline. In some instances, the use of more than one antenna may bereferred to as MIMO. In certain embodiments, antenna 162 may be separatefrom network node 160 and may be connectable to network node 160 throughan interface or port.

Antenna 162, interface 190, and/or processing circuitry 170 may beconfigured to perform any receiving operations and/or certain obtainingoperations described herein as being performed by a network node. Anyinformation, data and/or signals may be received from a wireless device,another network node and/or any other network equipment. Similarly,antenna 162, interface 190, and/or processing circuitry 170 may beconfigured to perform any transmitting operations described herein asbeing performed by a network node. Any information, data and/or signalsmay be transmitted to a wireless device, another network node and/or anyother network equipment.

Power circuitry 187 may comprise, or be coupled to, power managementcircuitry and is configured to supply the components of network node 160with power for performing the functionality described herein. Powercircuitry 187 may receive power from power source 186. Power source 186and/or power circuitry 187 may be configured to provide power to thevarious components of network node 160 in a form suitable for therespective components (e.g., at a voltage and current level needed foreach respective component). Power source 186 may either be included in,or external to, power circuitry 187 and/or network node 160. Forexample, network node 160 may be connectable to an external power source(e.g., an electricity outlet) via an input circuitry or interface suchas an electrical cable, whereby the external power source supplies powerto power circuitry 187. As a further example, power source 186 maycomprise a source of power in the form of a battery or battery packwhich is connected to, or integrated in, power circuitry 187. Thebattery may provide backup power should the external power source fail.Other types of power sources, such as photovoltaic devices, may also beused.

Alternative embodiments of network node 160 may include additionalcomponents beyond those shown in FIG. 6 that may be responsible forproviding certain aspects of the network node's functionality, includingany of the functionality described herein and/or any functionalitynecessary to support the subject matter described herein. For example,network node 160 may include user interface equipment to allow input ofinformation into network node 160 and to allow output of informationfrom network node 160. This may allow a user to perform diagnostic,maintenance, repair, and other administrative functions for network node160.

As used herein, wireless device (WD) refers to a device capable,configured, arranged and/or operable to communicate wirelessly withnetwork nodes and/or other wireless devices. Unless otherwise noted, theterm WD may be used interchangeably herein with user equipment (UE).Communicating wirelessly may involve transmitting and/or receivingwireless signals using electromagnetic waves, radio waves, infraredwaves, and/or other types of signals suitable for conveying informationthrough air. In some embodiments, a WD may be configured to transmitand/or receive information without direct human interaction. Forinstance, a WD may be designed to transmit information to a network on apredetermined schedule, when triggered by an internal or external event,or in response to requests from the network. Examples of a WD include,but are not limited to, a smart phone, a mobile phone, a cell phone, avoice over IP (VoIP) phone, a wireless local loop phone, a desktopcomputer, a personal digital assistant (PDA), a wireless cameras, agaming console or device, a music storage device, a playback appliance,a wearable terminal device, a wireless endpoint, a mobile station, atablet, a laptop, a laptop-embedded equipment (LEE), a laptop-mountedequipment (LME), a smart device, a wireless customer-premise equipment(CPE), a vehicle-mounted wireless terminal device, etc. A WD may supportdevice-to-device (D2D) communication, for example by implementing a 3GPPstandard for sidelink communication, vehicle-to-vehicle (V2V),vehicle-to-infrastructure (V2I), vehicle-to-everything (V2X) and may inthis case be referred to as a D2D communication device. As yet anotherspecific example, in an Internet of Things (IoT) scenario, a WD mayrepresent a machine or other device that performs monitoring and/ormeasurements, and transmits the results of such monitoring and/ormeasurements to another WD and/or a network node. The WD may in thiscase be a machine-to-machine (M2M) device, which may in a 3GPP contextbe referred to as an MTC device. As one particular example, the WD maybe a UE implementing the 3GPP narrow band internet of things (NB-IoT)standard. Particular examples of such machines or devices are sensors,metering devices such as power meters, industrial machinery, or home orpersonal appliances (e.g., refrigerators, televisions, etc.) personalwearables (e.g., watches, fitness trackers, etc.). In other scenarios, aWD may represent a vehicle or other equipment that is capable ofmonitoring and/or reporting on its operational status or other functionsassociated with its operation. A WD as described above may represent theendpoint of a wireless connection, in which case the device may bereferred to as a wireless terminal. Furthermore, a WD as described abovemay be mobile, in which case it may also be referred to as a mobiledevice or a mobile terminal.

As illustrated, wireless device 110 includes antenna 111, interface 114,processing circuitry 120, device readable medium 130, user interfaceequipment 132, auxiliary equipment 134, power source 136 and powercircuitry 137. WD 110 may include multiple sets of one or more of theillustrated components for different wireless technologies supported byWD 110, such as, for example, GSM, WCDMA, LTE, NR, WiFi, WiMAX, orBluetooth wireless technologies, just to mention a few. These wirelesstechnologies may be integrated into the same or different chips or setof chips as other components within WD 110.

Antenna 111 may include one or more antennas or antenna arrays,configured to send and/or receive wireless signals, and is connected tointerface 114. In certain alternative embodiments, antenna 111 may beseparate from WD 110 and be connectable to WD 110 through an interfaceor port. Antenna 111, interface 114, and/or processing circuitry 120 maybe configured to perform any receiving or transmitting operationsdescribed herein as being performed by a WD. Any information, dataand/or signals may be received from a network node and/or another WD. Insome embodiments, radio front end circuitry and/or antenna 111 may beconsidered an interface.

As illustrated, interface 114 comprises radio front end circuitry 112and antenna 111. Radio front end circuitry 112 comprise one or morefilters 118 and amplifiers 116. Radio front end circuitry 114 isconnected to antenna 111 and processing circuitry 120, and is configuredto condition signals communicated between antenna 111 and processingcircuitry 120. Radio front end circuitry 112 may be coupled to or a partof antenna 111. In some embodiments, WD 110 may not include separateradio front end circuitry 112; rather, processing circuitry 120 maycomprise radio front end circuitry and may be connected to antenna 111.Similarly, in some embodiments, some or all of RF transceiver circuitry122 may be considered a part of interface 114. Radio front end circuitry112 may receive digital data that is to be sent out to other networknodes or WDs via a wireless connection. Radio front end circuitry 112may convert the digital data into a radio signal having the appropriatechannel and bandwidth parameters using a combination of filters 118and/or amplifiers 116. The radio signal may then be transmitted viaantenna 111. Similarly, when receiving data, antenna 111 may collectradio signals which are then converted into digital data by radio frontend circuitry 112. The digital data may be passed to processingcircuitry 120. In other embodiments, the interface may comprisedifferent components and/or different combinations of components.

Processing circuitry 120 may comprise a combination of one or more of amicroprocessor, controller, microcontroller, central processing unit,digital signal processor, application-specific integrated circuit, fieldprogrammable gate array, or any other suitable computing device,resource, or combination of hardware, software, and/or encoded logicoperable to provide, either alone or in conjunction with other WD 110components, such as device readable medium 130, WD 110 functionality.Such functionality may include providing any of the various wirelessfeatures or benefits discussed herein. For example, processing circuitry120 may execute instructions stored in device readable medium 130 or inmemory within processing circuitry 120 to provide the functionalitydisclosed herein.

As illustrated, processing circuitry 120 includes one or more of RFtransceiver circuitry 122, baseband processing circuitry 124, andapplication processing circuitry 126. In other embodiments, theprocessing circuitry may comprise different components and/or differentcombinations of components. In certain embodiments processing circuitry120 of WD 110 may comprise a SOC. In some embodiments, RF transceivercircuitry 122, baseband processing circuitry 124, and applicationprocessing circuitry 126 may be on separate chips or sets of chips. Inalternative embodiments, part or all of baseband processing circuitry124 and application processing circuitry 126 may be combined into onechip or set of chips, and RF transceiver circuitry 122 may be on aseparate chip or set of chips. In still alternative embodiments, part orall of RF transceiver circuitry 122 and baseband processing circuitry124 may be on the same chip or set of chips, and application processingcircuitry 126 may be on a separate chip or set of chips. In yet otheralternative embodiments, part or all of RF transceiver circuitry 122,baseband processing circuitry 124, and application processing circuitry126 may be combined in the same chip or set of chips. In someembodiments, RF transceiver circuitry 122 may be a part of interface114. RF transceiver circuitry 122 may condition RF signals forprocessing circuitry 120.

In certain embodiments, some or all of the functionality describedherein as being performed by a WD may be provided by processingcircuitry 120 executing instructions stored on device readable medium130, which in certain embodiments may be a computer-readable storagemedium. In alternative embodiments, some or all of the functionality maybe provided by processing circuitry 120 without executing instructionsstored on a separate or discrete device readable storage medium, such asin a hard-wired manner. In any of those particular embodiments, whetherexecuting instructions stored on a device readable storage medium ornot, processing circuitry 120 can be configured to perform the describedfunctionality. The benefits provided by such functionality are notlimited to processing circuitry 120 alone or to other components of WD110, but are enjoyed by WD 110 as a whole, and/or by end users and thewireless network generally.

Processing circuitry 120 may be configured to perform any determining,calculating, or similar operations (e.g., certain obtaining operations)described herein as being performed by a WD. These operations, asperformed by processing circuitry 120, may include processinginformation obtained by processing circuitry 120 by, for example,converting the obtained information into other information, comparingthe obtained information or converted information to information storedby WD 110, and/or performing one or more operations based on theobtained information or converted information, and as a result of saidprocessing making a determination.

Device readable medium 130 may be operable to store a computer program,software, an application including one or more of logic, rules, code,tables, etc. and/or other instructions capable of being executed byprocessing circuitry 120. Device readable medium 130 may includecomputer memory (e.g., Random Access Memory (RAM) or Read Only Memory(ROM)), mass storage media (e.g., a hard disk), removable storage media(e.g., a Compact Disk (CD) or a Digital Video Disk (DVD)), and/or anyother volatile or non-volatile, non-transitory device readable and/orcomputer executable memory devices that store information, data, and/orinstructions that may be used by processing circuitry 120. In someembodiments, processing circuitry 120 and device readable medium 130 maybe considered to be integrated.

User interface equipment 132 may provide components that allow for ahuman user to interact with WD 110. Such interaction may be of manyforms, such as visual, audial, tactile, etc. User interface equipment132 may be operable to produce output to the user and to allow the userto provide input to WD 110. The type of interaction may vary dependingon the type of user interface equipment 132 installed in WD 110. Forexample, if WD 110 is a smart phone, the interaction may be via a touchscreen; if WD 110 is a smart meter, the interaction may be through ascreen that provides usage (e.g., the number of gallons used) or aspeaker that provides an audible alert (e.g., if smoke is detected).User interface equipment 132 may include input interfaces, devices andcircuits, and output interfaces, devices and circuits. User interfaceequipment 132 is configured to allow input of information into WD 110,and is connected to processing circuitry 120 to allow processingcircuitry 120 to process the input information. User interface equipment132 may include, for example, a microphone, a proximity or other sensor,keys/buttons, a touch display, one or more cameras, a USB port, or otherinput circuitry. User interface equipment 132 is also configured toallow output of information from WD 110, and to allow processingcircuitry 120 to output information from WD 110. User interfaceequipment 132 may include, for example, a speaker, a display, vibratingcircuitry, a USB port, a headphone interface, or other output circuitry.Using one or more input and output interfaces, devices, and circuits, ofuser interface equipment 132, WD 110 may communicate with end usersand/or the wireless network, and allow them to benefit from thefunctionality described herein.

Auxiliary equipment 134 is operable to provide more specificfunctionality which may not be generally performed by WDs. This maycomprise specialized sensors for doing measurements for variouspurposes, interfaces for additional types of communication such as wiredcommunications etc. The inclusion and type of components of auxiliaryequipment 134 may vary depending on the embodiment and/or scenario.

Power source 136 may, in some embodiments, be in the form of a batteryor battery pack. Other types of power sources, such as an external powersource (e.g., an electricity outlet), photovoltaic devices or powercells, may also be used. WD 110 may further comprise power circuitry 137for delivering power from power source 136 to the various parts of WD110 which need power from power source 136 to carry out anyfunctionality described or indicated herein. Power circuitry 137 may incertain embodiments comprise power management circuitry. Power circuitry137 may additionally or alternatively be operable to receive power froman external power source; in which case WD 110 may be connectable to theexternal power source (such as an electricity outlet) via inputcircuitry or an interface such as an electrical power cable. Powercircuitry 137 may also in certain embodiments be operable to deliverpower from an external power source to power source 136. This may be,for example, for the charging of power source 136. Power circuitry 137may perform any formatting, converting, or other modification to thepower from power source 136 to make the power suitable for therespective components of WD 110 to which power is supplied.

FIG. 7 illustrates one embodiment of a UE in accordance with variousaspects described herein. As used herein, a user equipment or UE may notnecessarily have a user in the sense of a human user who owns and/oroperates the relevant device. Instead, a UE may represent a device thatis intended for sale to, or operation by, a human user but which maynot, or which may not initially, be associated with a specific humanuser (e.g., a smart sprinkler controller). Alternatively, a UE mayrepresent a device that is not intended for sale to, or operation by, anend user but which may be associated with or operated for the benefit ofa user (e.g., a smart power meter). UE 2200 may be any UE identified bythe 3^(rd) Generation Partnership Project (3GPP), including a NB-IoT UE,a machine type communication (MTC) UE, and/or an enhanced MTC (eMTC) UE.UE 200, as illustrated in FIG. 7 , is one example of a WD configured forcommunication in accordance with one or more communication standardspromulgated by the 3rd Generation Partnership Project (3GPP), such as3GPP's GSM, UMTS, LTE, and/or 5G standards. As mentioned previously, theterm WD and UE may be used interchangeable. Accordingly, although FIG. 7is a UE, the components discussed herein are equally applicable to a WD,and vice-versa.

In FIG. 7 , UE 200 includes processing circuitry 201 that is operativelycoupled to input/output interface 205, radio frequency (RF) interface209, network connection interface 211, memory 215 including randomaccess memory (RAM) 217, read-only memory (ROM) 219, and storage medium221 or the like, communication subsystem 231, power source 213, and/orany other component, or any combination thereof. Storage medium 221includes operating system 223, application program 225, and data 227. Inother embodiments, storage medium 221 may include other similar types ofinformation. Certain UEs may utilize all of the components shown in FIG.7 , or only a subset of the components. The level of integration betweenthe components may vary from one UE to another UE. Further, certain UEsmay contain multiple instances of a component, such as multipleprocessors, memories, transceivers, transmitters, receivers, etc.

In FIG. 7 , processing circuitry 201 may be configured to processcomputer instructions and data. Processing circuitry 201 may beconfigured to implement any sequential state machine operative toexecute machine instructions stored as machine-readable computerprograms in the memory, such as one or more hardware-implemented statemachines (e.g., in discrete logic, FPGA, ASIC, etc.); programmable logictogether with appropriate firmware; one or more stored program,general-purpose processors, such as a microprocessor or Digital SignalProcessor (DSP), together with appropriate software; or any combinationof the above. For example, the processing circuitry 201 may include twocentral processing units (CPUs). Data may be information in a formsuitable for use by a computer.

In the depicted embodiment, input/output interface 205 may be configuredto provide a communication interface to an input device, output device,or input and output device. UE 200 may be configured to use an outputdevice via input/output interface 205. An output device may use the sametype of interface port as an input device. For example, a USB port maybe used to provide input to and output from UE 200. The output devicemay be a speaker, a sound card, a video card, a display, a monitor, aprinter, an actuator, an emitter, a smartcard, another output device, orany combination thereof. UE 200 may be configured to use an input devicevia input/output interface 205 to allow a user to capture informationinto UE 200. The input device may include a touch-sensitive orpresence-sensitive display, a camera (e.g., a digital camera, a digitalvideo camera, a web camera, etc.), a microphone, a sensor, a mouse, atrackball, a directional pad, a trackpad, a scroll wheel, a smartcard,and the like. The presence-sensitive display may include a capacitive orresistive touch sensor to sense input from a user. A sensor may be, forinstance, an accelerometer, a gyroscope, a tilt sensor, a force sensor,a magnetometer, an optical sensor, a proximity sensor, another likesensor, or any combination thereof. For example, the input device may bean accelerometer, a magnetometer, a digital camera, a microphone, and anoptical sensor.

In FIG. 7 , RF interface 209 may be configured to provide acommunication interface to RF components such as a transmitter, areceiver, and an antenna. Network connection interface 211 may beconfigured to provide a communication interface to network 243 a.Network 243 a may encompass wired and/or wireless networks such as alocal-area network (LAN), a wide-area network (WAN), a computer network,a wireless network, a telecommunications network, another like networkor any combination thereof. For example, network 243 a may comprise aWi-Fi network. Network connection interface 211 may be configured toinclude a receiver and a transmitter interface used to communicate withone or more other devices over a communication network according to oneor more communication protocols, such as Ethernet, TCP/IP, SONET, ATM,or the like. Network connection interface 211 may implement receiver andtransmitter functionality appropriate to the communication network links(e.g., optical, electrical, and the like). The transmitter and receiverfunctions may share circuit components, software or firmware, oralternatively may be implemented separately.

RAM 217 may be configured to interface via bus 202 to processingcircuitry 201 to provide storage or caching of data or computerinstructions during the execution of software programs such as theoperating system, application programs, and device drivers. ROM 219 maybe configured to provide computer instructions or data to processingcircuitry 201. For example, ROM 219 may be configured to store invariantlow-level system code or data for basic system functions such as basicinput and output (I/O), startup, or reception of keystrokes from akeyboard that are stored in a non-volatile memory. Storage medium 221may be configured to include memory such as RAM, ROM, programmableread-only memory (PROM), erasable programmable read-only memory (EPROM),electrically erasable programmable read-only memory (EEPROM), magneticdisks, optical disks, floppy disks, hard disks, removable cartridges, orflash drives. In one example, storage medium 221 may be configured toinclude operating system 223, application program 225 such as a webbrowser application, a widget or gadget engine or another application,and data file 227. Storage medium 221 may store, for use by UE 200, anyof a variety of various operating systems or combinations of operatingsystems.

Storage medium 221 may be configured to include a number of physicaldrive units, such as redundant array of independent disks (RAID), floppydisk drive, flash memory, USB flash drive, external hard disk drive,thumb drive, pen drive, key drive, high-density digital versatile disc(HD-DVD) optical disc drive, internal hard disk drive, Blu-Ray opticaldisc drive, holographic digital data storage (HDDS) optical disc drive,external mini-dual in-line memory module (DIMM), synchronous dynamicrandom access memory (SDRAM), external micro-DIMM SDRAM, smartcardmemory such as a subscriber identity module or a removable user identity(SIM/RUIM) module, other memory, or any combination thereof. Storagemedium 221 may allow UE 200 to access computer-executable instructions,application programs or the like, stored on transitory or non-transitorymemory media, to off-load data, or to upload data. An article ofmanufacture, such as one utilizing a communication system may betangibly embodied in storage medium 221, which may comprise a devicereadable medium.

In FIG. 7 , processing circuitry 201 may be configured to communicatewith network 243 b using communication subsystem 231. Network 243 a andnetwork 243 b may be the same network or networks or different networkor networks. Communication subsystem 231 may be configured to includeone or more transceivers used to communicate with network 243 b. Forexample, communication subsystem 231 may be configured to include one ormore transceivers used to communicate with one or more remotetransceivers of another device capable of wireless communication such asanother WD, UE, or base station of a radio access network (RAN)according to one or more communication protocols, such as IEEE 802.2,CDMA, WCDMA, GSM, LTE, UTRAN, WiMax, or the like. Each transceiver mayinclude transmitter 233 and/or receiver 235 to implement transmitter orreceiver functionality, respectively, appropriate to the RAN links(e.g., frequency allocations and the like). Further, transmitter 233 andreceiver 235 of each transceiver may share circuit components, softwareor firmware, or alternatively may be implemented separately.

In the illustrated embodiment, the communication functions ofcommunication subsystem 231 may include data communication, voicecommunication, multimedia communication, short-range communications suchas Bluetooth, near-field communication, location-based communicationsuch as the use of the global positioning system (GPS) to determine alocation, another like communication function, or any combinationthereof. For example, communication subsystem 231 may include cellularcommunication, Wi-Fi communication, Bluetooth communication, and GPScommunication. Network 243 b may encompass wired and/or wirelessnetworks such as a local-area network (LAN), a wide-area network (WAN),a computer network, a wireless network, a telecommunications network,another like network or any combination thereof. For example, network243 b may be a cellular network, a Wi-Fi network, and/or a near-fieldnetwork. Power source 213 may be configured to provide alternatingcurrent (AC) or direct current (DC) power to components of UE 200.

The features, benefits and/or functions described herein may beimplemented in one of the components of UE 200 or partitioned acrossmultiple components of UE 200. Further, the features, benefits, and/orfunctions described herein may be implemented in any combination ofhardware, software or firmware. In one example, communication subsystem231 may be configured to include any of the components described herein.Further, processing circuitry 201 may be configured to communicate withany of such components over bus 202. In another example, any of suchcomponents may be represented by program instructions stored in memorythat when executed by processing circuitry 201 perform the correspondingfunctions described herein. In another example, the functionality of anyof such components may be partitioned between processing circuitry 201and communication subsystem 231. In another example, thenon-computationally intensive functions of any of such components may beimplemented in software or firmware and the computationally intensivefunctions may be implemented in hardware.

Appendix A

Hereinafter, further example embodiments related to NR resourceallocation design issues are discussed, and more specifically timedomain resource allocation.

Time Allocation

In 3GPP RAN1 #90bis meeting the following was agreed:

Agreements:

-   -   For both slot and mini-slot, the scheduling DCI can provide an        index into a UE-specific table giving the OFDM symbols used for        the PDSCH (or PUSCH) transmission        -   starting OFDM symbol and length in OFDM symbols of the            allocation        -   For Further Study (FFS): one or more tables        -   FFS: including the slots used in case of            multi-slot/multi-mini-slot scheduling or slot index for            cross-slot scheduling        -   FFS: May need to revisit if SFI support non-contiguous            allocations    -   At least for RMSI scheduling        -   At least one table entry needs to be fixed in the spec

Regarding whether one or more tables should be specified, it is believedthat multiple tables can provide more flexibility in scheduling.However, in order to limit the DCI message size to select the tables,the number of tables may be limited to two. The table entries in the twotables can differ in starting OFDM symbol and/or duration. The selectionof tables can be based on other fields in DCI message such as whetherType A or Type B scheduling is used, or a field that signals whetherslot-based or mini-slot based transmission is scheduled.

Proposal 3-1: To provide more flexibility in time domain resourceallocation, two tables are specified with different starting OFDM symboland duration in OFDM symbols.

For NR, data transmission may occupy (almost) all OFDM symbols in a slotor, in case of a mini-slot transmission, only some of them. Thesepossibilities can be handled in a unified way by including informationin the DCI about the PUSCH and PDSCH the starting and ending position.To limit the DCI overhead while at the same time provide someflexibility one possibility is to have, e.g., 3 bits in the DCI pointinginto different combinations of starting and ending positions.

The combinations should also be aligned with OFDM symbol positions givenby SFI (slot format indicator) in group common PDCCH (e.g., thecombinations shown in [1]). For DL, the reference for starting andending positions should be with respect to the first OFDM symbol of thePDCCH carrying the corresponding DCI. Some starting positions may be −vevalues to accommodate the cases where PDSCH starts before the symbol inwhich PDCCH coreset is configured. To limit UE buffering requirements,only limited −ve values should be allowed (e.g., only −2, −1).

Data may also span multiple slots in case of slotaggregation/repetition. To handle slot aggregation, the UE assumes thesame time resource allocation in slots wherein the transmission isrepeated.

Proposal 3-2: When slot aggregation/repetition is applied, the UEassumes the same time resource allocation in slots wherein thetransmission is repeated.

To have more efficiency in DCI message it would be possible to make thebit fields in the DCI message depending on which CORESET the DCI istransmitted from. This is to allow more appropriate options ofconfigurations of the starting and stop OFDM symbols for PDSCH andPUSCH.

Proposal 3-3: The bitfield in the DCI message indicating the startingand ending OFDM symbol within a slot is configured separately perCORESET.

Furthermore, for UL and DL in some cases there would be a need to definein which slot the transmission of PUSCH or PDSCH should occur in. Suchinformation could either be a separate bitfield or be jointly encodedwith the starting and ending position. It is noted here however that tobe able to support rather long periods of UL slot there would be a needfor around 4 bits to support these cases. A similar need does notstrictly exist for DL as in DL a DCI message can be provided in each DLslot so for DL the information could be joint coded with the locationinformation within the slot or a single bit could be introduced toindicate scheduling in the next preceding slot.

Proposal 3-4

-   -   For PUSCH transmissions, an bitfield of up to 4 bits is        introduced in the DCI message to indicate which UL slot the        PUSCH is transmitted within    -   For PDSCH, indication of which DL slot the PDSCH is transmitted        is either joint coded with the location information within the        slot or a single bit could be introduced to indicate scheduling        in the next preceding slot.

Appendix B

Some additional embodiments contemplated herein will now be describedmore fully with reference to FIGS. 8-14 . FIG. 8 is a schematic blockdiagram illustrating a virtualization environment 300 in which functionsimplemented by some embodiments may be virtualized. In the presentcontext, virtualizing means creating virtual versions of apparatuses ordevices which may include virtualizing hardware platforms, storagedevices and networking resources. As used herein, virtualization can beapplied to a node (e.g., a virtualized base station or a virtualizedradio access node) or to a device (e.g., a UE, a wireless device or anyother type of communication device) or components thereof and relates toan implementation in which at least a portion of the functionality isimplemented as one or more virtual components (e.g., via one or moreapplications, components, functions, virtual machines or containersexecuting on one or more physical processing nodes in one or morenetworks).

In some embodiments, some or all of the functions described herein maybe implemented as virtual components executed by one or more virtualmachines implemented in one or more virtual environments 300 hosted byone or more of hardware nodes 330. Further, in embodiments in which thevirtual node is not a radio access node or does not require radioconnectivity (e.g., a core network node), then the network node may beentirely virtualized.

The functions may be implemented by one or more applications 320 (whichmay alternatively be called software instances, virtual appliances,network functions, virtual nodes, virtual network functions, etc.)operative to implement some of the features, functions, and/or benefitsof some of the embodiments disclosed herein. Applications 320 are run invirtualization environment 300 which provides hardware 330 comprisingprocessing circuitry 360 and memory 390. Memory 390 containsinstructions 395 executable by processing circuitry 360 wherebyapplication 320 is operative to provide one or more of the features,benefits, and/or functions disclosed herein.

Virtualization environment 300, comprises general-purpose orspecial-purpose network hardware devices 330 comprising a set of one ormore processors or processing circuitry 360, which may be commercialoff-the-shelf (COTS) processors, dedicated Application SpecificIntegrated Circuits (ASICs), or any other type of processing circuitryincluding digital or analog hardware components or special purposeprocessors. Each hardware device may comprise memory 390-1 which may benon-persistent memory for temporarily storing instructions 395 orsoftware executed by processing circuitry 360. Each hardware device maycomprise one or more network interface controllers (NICs) 370, alsoknown as network interface cards, which include physical networkinterface 380. Each hardware device may also include non-transitory,persistent, machine-readable storage media 390-2 having stored thereinsoftware 395 and/or instructions executable by processing circuitry 360.Software 395 may include any type of software including software forinstantiating one or more virtualization layers 350 (also referred to ashypervisors), software to execute virtual machines 340 as well assoftware allowing it to execute functions, features and/or benefitsdescribed in relation with some embodiments described herein.

Virtual machines 340, comprise virtual processing, virtual memory,virtual networking or interface and virtual storage, and may be run by acorresponding virtualization layer 350 or hypervisor. Differentembodiments of the instance of virtual appliance 320 may be implementedon one or more of virtual machines 340, and the implementations may bemade in different ways.

During operation, processing circuitry 360 executes software 395 toinstantiate the hypervisor or virtualization layer 350, which maysometimes be referred to as a virtual machine monitor (VMM).Virtualization layer 350 may present a virtual operating platform thatappears like networking hardware to virtual machine 340.

As shown in FIG. 8 , hardware 330 may be a standalone network node withgeneric or specific components. Hardware 330 may comprise antenna 3225and may implement some functions via virtualization. Alternatively,hardware 330 may be part of a larger cluster of hardware (e.g., such asin a data center or customer premise equipment (CPE)) where manyhardware nodes work together and are managed via management andorchestration (MANO) 3100, which, among others, oversees lifecyclemanagement of applications 320.

Virtualization of the hardware is in some contexts referred to asnetwork function virtualization (NFV). NFV may be used to consolidatemany network equipment types onto industry standard high volume serverhardware, physical switches, and physical storage, which can be locatedin data centers, and customer premise equipment.

In the context of NFV, virtual machine 340 may be a softwareimplementation of a physical machine that runs programs as if they wereexecuting on a physical, non-virtualized machine. Each of virtualmachines 340, and that part of hardware 330 that executes that virtualmachine, be it hardware dedicated to that virtual machine and/orhardware shared by that virtual machine with others of the virtualmachines 340, forms a separate virtual network elements (VNE).

Still in the context of NFV, Virtual Network Function (VNF) isresponsible for handling specific network functions that run in one ormore virtual machines 340 on top of hardware networking infrastructure330 and corresponds to application 320 in FIG. 8 .

In some embodiments, one or more radio units 3200 that each include oneor more transmitters 3220 and one or more receivers 3210 may be coupledto one or more antennas 3225. Radio units 3200 may communicate directlywith hardware nodes 330 via one or more appropriate network interfacesand may be used in combination with the virtual components to provide avirtual node with radio capabilities, such as a radio access node or abase station.

In some embodiments, some signalling can be effected with the use ofcontrol system 3230 which may alternatively be used for communicationbetween the hardware nodes 330 and radio units 3200.

With reference to FIG. 9 , in accordance with an embodiment, acommunication system includes telecommunication network 410, such as a3GPP-type cellular network, which comprises access network 411, such asa radio access network, and core network 414. Access network 411comprises a plurality of base stations 412 a, 412 b, 412 c, such as NBs,eNBs, gNBs or other types of wireless access points, each defining acorresponding coverage area 413 a, 413 b, 413 c. Each base station 412a, 412 b, 412 c is connectable to core network 414 over a wired orwireless connection 415. A first UE 491 located in coverage area 413 cis configured to wirelessly connect to, or be paged by, thecorresponding base station 412 c. A second UE 492 in coverage area 413 ais wirelessly connectable to the corresponding base station 412 a. Whilea plurality of UEs 491, 492 are illustrated in this example, thedisclosed embodiments are equally applicable to a situation where a soleUE is in the coverage area or where a sole UE is connecting to thecorresponding base station 412.

Telecommunication network 410 is itself connected to host computer 430,which may be embodied in the hardware and/or software of a standaloneserver, a cloud-implemented server, a distributed server or asprocessing resources in a server farm. Host computer 430 may be underthe ownership or control of a service provider, or may be operated bythe service provider or on behalf of the service provider. Connections421 and 422 between telecommunication network 410 and host computer 430may extend directly from core network 414 to host computer 430 or may govia an optional intermediate network 420. Intermediate network 420 maybe one of, or a combination of more than one of, a public, private orhosted network; intermediate network 420, if any, may be a backbonenetwork or the Internet; in particular, intermediate network 420 maycomprise two or more sub-networks (not shown).

The communication system of FIG. 9 as a whole enables connectivitybetween the connected UEs 491, 492 and host computer 430. Theconnectivity may be described as an over-the-top (OTT) connection 450.Host computer 430 and the connected UEs 491, 492 are configured tocommunicate data and/or signaling via OTT connection 450, using accessnetwork 411, core network 414, any intermediate network 420 and possiblefurther infrastructure (not shown) as intermediaries. OTT connection 450may be transparent in the sense that the participating communicationdevices through which OTT connection 450 passes are unaware of routingof uplink and downlink communications. For example, base station 412 maynot or need not be informed about the past routing of an incomingdownlink communication with data originating from host computer 430 tobe forwarded (e.g., handed over) to a connected UE 491. Similarly, basestation 412 need not be aware of the future routing of an outgoinguplink communication originating from the UE 491 towards the hostcomputer 430.

Example implementations, in accordance with an embodiment, of the UE,base station and host computer discussed in the preceding paragraphswill now be described with reference to FIG. 10 . In communicationsystem 500, host computer 510 comprises hardware 515 includingcommunication interface 516 configured to set up and maintain a wired orwireless connection with an interface of a different communicationdevice of communication system 500. Host computer 510 further comprisesprocessing circuitry 518, which may have storage and/or processingcapabilities. In particular, processing circuitry 518 may comprise oneor more programmable processors, application-specific integratedcircuits, field programmable gate arrays or combinations of these (notshown) adapted to execute instructions. Host computer 510 furthercomprises software 511, which is stored in or accessible by hostcomputer 510 and executable by processing circuitry 518. Software 511includes host application 512. Host application 512 may be operable toprovide a service to a remote user, such as UE 530 connecting via OTTconnection 550 terminating at UE 530 and host computer 510. In providingthe service to the remote user, host application 512 may provide userdata which is transmitted using OTT connection 550.

Communication system 500 further includes base station 520 provided in atelecommunication system and comprising hardware 525 enabling it tocommunicate with host computer 510 and with UE 530. Hardware 525 mayinclude communication interface 526 for setting up and maintaining awired or wireless connection with an interface of a differentcommunication device of communication system 500, as well as radiointerface 527 for setting up and maintaining at least wirelessconnection 570 with UE 530 located in a coverage area (not shown in FIG.10 ) served by base station 520. Communication interface 526 may beconfigured to facilitate connection 560 to host computer 510. Connection560 may be direct or it may pass through a core network (not shown inFIG. 10 ) of the telecommunication system and/or through one or moreintermediate networks outside the telecommunication system. In theembodiment shown, hardware 525 of base station 520 further includesprocessing circuitry 528, which may comprise one or more programmableprocessors, application-specific integrated circuits, field programmablegate arrays or combinations of these (not shown) adapted to executeinstructions. Base station 520 further has software 521 storedinternally or accessible via an external connection.

Communication system 500 further includes UE 530 already referred to.Its hardware 535 may include radio interface 537 configured to set upand maintain wireless connection 570 with a base station serving acoverage area in which UE 530 is currently located. Hardware 535 of UE530 further includes processing circuitry 538, which may comprise one ormore programmable processors, application-specific integrated circuits,field programmable gate arrays or combinations of these (not shown)adapted to execute instructions. UE 530 further comprises software 531,which is stored in or accessible by UE 530 and executable by processingcircuitry 538. Software 531 includes client application 532. Clientapplication 532 may be operable to provide a service to a human ornon-human user via UE 530, with the support of host computer 510. Inhost computer 510, an executing host application 512 may communicatewith the executing client application 532 via OTT connection 550terminating at UE 530 and host computer 510. In providing the service tothe user, client application 532 may receive request data from hostapplication 512 and provide user data in response to the request data.OTT connection 550 may transfer both the request data and the user data.Client application 532 may interact with the user to generate the userdata that it provides.

It is noted that host computer 510, base station 520 and UE 530illustrated in FIG. 10 may be similar or identical to host computer 430,one of base stations 412 a, 412 b, 412 c and one of UEs 491, 492 of FIG.9 , respectively. This is to say, the inner workings of these entitiesmay be as shown in FIG. 10 and independently, the surrounding networktopology may be that of FIG. 9 .

In FIG. 10 , OTT connection 550 has been drawn abstractly to illustratethe communication between host computer 510 and UE 530 via base station520, without explicit reference to any intermediary devices and theprecise routing of messages via these devices. Network infrastructuremay determine the routing, which it may be configured to hide from UE530 or from the service provider operating host computer 510, or both.While OTT connection 550 is active, the network infrastructure mayfurther take decisions by which it dynamically changes the routing(e.g., on the basis of load balancing consideration or reconfigurationof the network).

Wireless connection 570 between UE 530 and base station 520 is inaccordance with the teachings of the embodiments described throughoutthis disclosure. One or more of the various embodiments improve theperformance of OTT services provided to UE 530 using OTT connection 550,in which wireless connection 570 forms the last segment. More precisely,the teachings of these embodiments may improve the data rate andlatency, for example, by allowing for more flexible scheduling oftime-domain resources, and thereby provide benefits such as reduced userwaiting time.

A measurement procedure may be provided for the purpose of monitoringdata rate, latency and other factors on which the one or moreembodiments improve. There may further be an optional networkfunctionality for reconfiguring OTT connection 550 between host computer510 and UE 530, in response to variations in the measurement results.The measurement procedure and/or the network functionality forreconfiguring OTT connection 550 may be implemented in software 511 andhardware 515 of host computer 510 or in software 531 and hardware 535 ofUE 530, or both. In embodiments, sensors (not shown) may be deployed inor in association with communication devices through which OTTconnection 550 passes; the sensors may participate in the measurementprocedure by supplying values of the monitored quantities exemplifiedabove, or supplying values of other physical quantities from whichsoftware 511, 531 may compute or estimate the monitored quantities. Thereconfiguring of OTT connection 550 may include message format,retransmission settings, preferred routing etc.; the reconfiguring neednot affect base station 520, and it may be unknown or imperceptible tobase station 520. Such procedures and functionalities may be known andpracticed in the art. In certain embodiments, measurements may involveproprietary UE signaling facilitating host computer 510's measurementsof throughput, propagation times, latency and the like. The measurementsmay be implemented in that software 511 and 531 causes messages to betransmitted, in particular empty or ‘dummy’ messages, using OTTconnection 550 while it monitors propagation times, errors etc.

FIG. 11 is a flowchart illustrating a method implemented in acommunication system, in accordance with one embodiment. Thecommunication system includes a host computer, a base station and a UEwhich may be those described with reference to FIGS. 9 and 10 . Forsimplicity of the present disclosure, only drawing references to FIG. 11will be included in this section. In step 610, the host computerprovides user data. In substep 611 (which may be optional) of step 610,the host computer provides the user data by executing a hostapplication. In step 620, the host computer initiates a transmissioncarrying the user data to the UE. In step 630 (which may be optional),the base station transmits to the UE the user data which was carried inthe transmission that the host computer initiated, in accordance withthe teachings of the embodiments described throughout this disclosure.In step 640 (which may also be optional), the UE executes a clientapplication associated with the host application executed by the hostcomputer.

FIG. 12 is a flowchart illustrating a method implemented in acommunication system, in accordance with one embodiment. Thecommunication system includes a host computer, a base station and a UEwhich may be those described with reference to FIGS. 9 and 10 . Forsimplicity of the present disclosure, only drawing references to FIG. 12will be included in this section. In step 710 of the method, the hostcomputer provides user data. In an optional substep (not shown) the hostcomputer provides the user data by executing a host application. In step720, the host computer initiates a transmission carrying the user datato the UE. The transmission may pass via the base station, in accordancewith the teachings of the embodiments described throughout thisdisclosure. In step 730 (which may be optional), the UE receives theuser data carried in the transmission.

FIG. 13 is a flowchart illustrating a method implemented in acommunication system, in accordance with one embodiment. Thecommunication system includes a host computer, a base station and a UEwhich may be those described with reference to FIGS. 9 and 10 . Forsimplicity of the present disclosure, only drawing references to FIG. 13will be included in this section. In step 810 (which may be optional),the UE receives input data provided by the host computer. Additionallyor alternatively, in step 820, the UE provides user data. In substep 821(which may be optional) of step 820, the UE provides the user data byexecuting a client application. In substep 811 (which may be optional)of step 810, the UE executes a client application which provides theuser data in reaction to the received input data provided by the hostcomputer. In providing the user data, the executed client applicationmay further consider user input received from the user. Regardless ofthe specific manner in which the user data was provided, the UEinitiates, in substep 830 (which may be optional), transmission of theuser data to the host computer. In step 840 of the method, the hostcomputer receives the user data transmitted from the UE, in accordancewith the teachings of the embodiments described throughout thisdisclosure.

FIG. 14 is a flowchart illustrating a method implemented in acommunication system, in accordance with one embodiment. Thecommunication system includes a host computer, a base station and a UEwhich may be those described with reference to FIGS. 9 and 10 . Forsimplicity of the present disclosure, only drawing references to FIG. 14will be included in this section. In step 910 (which may be optional),in accordance with the teachings of the embodiments described throughoutthis disclosure, the base station receives user data from the UE. Instep 920 (which may be optional), the base station initiatestransmission of the received user data to the host computer. In step 930(which may be optional), the host computer receives the user datacarried in the transmission initiated by the base station.

Group C Embodiments

-   -   39. A wireless device, configured to perform any of the steps of        any of the Group A embodiments.    -   40. A network node (e.g., base station), configured to perform        any of the steps of any of the Group B embodiments.    -   41. A wireless device, the wireless device comprising:        -   processing circuitry configured to perform any of the steps            of any of the Group A embodiments; and        -   power supply circuitry configured to supply power to the            wireless device.    -   42. A base station, the base station comprising:        -   processing circuitry configured to perform any of the steps            of any of the Group B embodiments;        -   power supply circuitry configured to supply power to the            wireless device.    -   43. A user equipment (UE), the UE comprising:        -   an antenna configured to send and receive wireless signals;        -   radio front-end circuitry connected to the antenna and to            processing circuitry, and configured to condition signals            communicated between the antenna and the processing            circuitry;        -   the processing circuitry being configured to perform any of            the steps of any of the Group A embodiments;        -   an input interface connected to the processing circuitry and            configured to allow input of information into the UE to be            processed by the processing circuitry;        -   an output interface connected to the processing circuitry            and configured to output information from the UE that has            been processed by the processing circuitry; and        -   a battery connected to the processing circuitry and            configured to supply power to the UE.    -   44. A communication system including a host computer comprising:        -   processing circuitry configured to provide user data; and        -   a communication interface configured to forward the user            data to a cellular network for transmission to a user            equipment (UE),        -   wherein the cellular network comprises a base station having            a radio interface and processing circuitry, the base            station's processing circuitry configured to perform any of            the steps of any of the Group B embodiments.    -   45. The communication system of the previous embodiment further        including the base station.    -   46. The communication system of the previous 2 embodiments,        further including the UE, wherein the UE is configured to        communicate with the base station.    -   47. The communication system of the previous 3 embodiments,        wherein:        -   the processing circuitry of the host computer is configured            to execute a host application, thereby providing the user            data; and        -   the UE comprises processing circuitry configured to execute            a client application associated with the host application.    -   48. A method implemented in a communication system including a        host computer, a base station and a user equipment (UE), the        method comprising:        -   at the host computer, providing user data; and        -   at the host computer, initiating a transmission carrying the            user data to the UE via a cellular network comprising the            base station, wherein the base station performs any of the            steps of any of the Group B embodiments.    -   49. The method of the previous embodiment, further comprising,        at the base station, transmitting the user data.    -   50. The method of the previous 2 embodiments, wherein the user        data is provided at the host computer by executing a host        application, the method further comprising, at the UE, executing        a client application associated with the host application.    -   51. A user equipment (UE) configured to communicate with a base        station, the UE comprising a radio interface and processing        circuitry configured to perform any of the of the methods of the        previous 3 embodiments.    -   52. A communication system including a host computer comprising:        -   processing circuitry configured to provide user data; and        -   a communication interface configured to forward user data to            a cellular network for transmission to a user equipment            (UE),        -   wherein the UE comprises a radio interface and processing            circuitry, the UE's components configured to perform any of            the steps of any of the Group A embodiments.    -   53. The communication system of the previous embodiment, wherein        the cellular network further includes a base station configured        to communicate with the UE.    -   54. The communication system of the previous 2 embodiments,        wherein:        -   the processing circuitry of the host computer is configured            to execute a host application, thereby providing the user            data; and        -   the UE's processing circuitry is configured to execute a            client application associated with the host application.    -   55. A method implemented in a communication system including a        host computer, a base station and a user equipment (UE), the        method comprising:        -   at the host computer, providing user data; and        -   at the host computer, initiating a transmission carrying the            user data to the UE via a cellular network comprising the            base station, wherein the UE performs any of the steps of            any of the Group A embodiments.    -   56. The method of the previous embodiment, further comprising at        the UE, receiving the user data from the base station.    -   57. A communication system including a host computer comprising:        -   communication interface configured to receive user data            originating from a transmission from a user equipment (UE)            to a base station,        -   wherein the UE comprises a radio interface and processing            circuitry, the UE's processing circuitry configured to            perform any of the steps of any of the Group A embodiments.    -   58. The communication system of the previous embodiment, further        including the UE.    -   59. The communication system of the previous 2 embodiments,        further including the base station, wherein the base station        comprises a radio interface configured to communicate with the        UE and a communication interface configured to forward to the        host computer the user data carried by a transmission from the        UE to the base station.    -   60. The communication system of the previous 3 embodiments,        wherein:        -   the processing circuitry of the host computer is configured            to execute a host application; and        -   the UE's processing circuitry is configured to execute a            client application associated with the host application,            thereby providing the user data.    -   61. The communication system of the previous 4 embodiments,        wherein:        -   the processing circuitry of the host computer is configured            to execute a host application, thereby providing request            data; and        -   the UE's processing circuitry is configured to execute a            client application associated with the host application,            thereby providing the user data in response to the request            data.    -   62. A method implemented in a communication system including a        host computer, a base station and a user equipment (UE), the        method comprising:        -   at the host computer, receiving user data transmitted to the            base station from the UE, wherein the UE performs any of the            steps of any of the Group A embodiments.    -   63. The method of the previous embodiment, further comprising,        at the UE, providing the user data to the base station.    -   64. The method of the previous 2 embodiments, further        comprising:        -   at the UE, executing a client application, thereby providing            the user data to be transmitted; and        -   at the host computer, executing a host application            associated with the client application.    -   65. The method of the previous 3 embodiments, further        comprising:        -   at the UE, executing a client application; and        -   at the UE, receiving input data to the client application,            the input data being provided at the host computer by            executing a host application associated with the client            application,        -   wherein the user data to be transmitted is provided by the            client application in response to the input data.    -   66. A communication system including a host computer comprising        a communication interface configured to receive user data        originating from a transmission from a user equipment (UE) to a        base station, wherein the base station comprises a radio        interface and processing circuitry, the base station's        processing circuitry configured to perform any of the steps of        any of the Group B embodiments.    -   67. The communication system of the previous embodiment further        including the base station.    -   68. The communication system of the previous 2 embodiments,        further including the UE, wherein the UE is configured to        communicate with the base station.    -   69. The communication system of the previous 3 embodiments,        wherein:        -   the processing circuitry of the host computer is configured            to execute a host application;        -   the UE is configured to execute a client application            associated with the host application, thereby providing the            user data to be received by the host computer.    -   70. A method implemented in a communication system including a        host computer, a base station and a user equipment (UE), the        method comprising:        -   at the host computer, receiving, from the base station, user            data originating from a transmission which the base station            has received from the UE, wherein the UE performs any of the            steps of any of the Group A embodiments.    -   71. The method of the previous embodiment, further comprising at        the base station, receiving the user data from the UE.    -   72. The method of the previous 2 embodiments, further comprising        at the base station, initiating a transmission of the received        user data to the host computer.

The invention claimed is:
 1. A method performed by a wireless device for determining a time-domain resource allocation, the method comprising: receiving from a network node a downlink control information, DCI, that schedules a downlink transmission; detecting a Radio Network Temporary Identifier, RNTI, used in the scheduling of the downlink transmission; selecting a time-domain resource allocation table from multiple different time-domain resource allocation tables based on the detected RNTI, wherein each of the different time domain resource allocation tables is defined by a plurality of entries that specify different combinations of starting orthogonal frequency division multiplexing, OFDM, symbol and duration in OFDM symbols for a time-domain resource allocation; and determining a time-domain resource allocation for the downlink transmission based on a time-domain resource allocation field in the DCI, the time-domain resource allocation field indicating an entry within the selected time-domain resource allocation table.
 2. The method of claim 1, wherein the multiple different time-domain resource allocation tables relate to time-domain resource allocation for physical downlink shared channel, PDSCH, scheduling.
 3. The method of claim 1, wherein the multiple different time-domain resource allocation tables comprise at least one pre-defined table with default values for the time domain resource allocation.
 4. The method of claim 1, wherein the multiple different time-domain resource allocation tables comprise at least one radio resource control, RRC, configured table.
 5. The method of claim 1, further comprising: receiving a physical downlink shared channel, PDSCH, on a time-domain resource corresponding to the determined time-domain resource allocation.
 6. The method of claim 1, wherein selecting the time-domain resource allocation table further comprises selecting the time-domain resource allocation table based on at least one of a Control Resource Set, CORESET, and a search space used for scheduling the downlink transmission.
 7. The method of claim 1, wherein a first table of the multiple different time-domain resource allocation tables comprises a different number of entries than a second table of the multiple different time-domain resource allocation tables.
 8. The method of claim 1, wherein the multiple different time-domain resource allocation tables comprise a same number of entries.
 9. A wireless device configured to determine a time-domain resource allocation, the wireless device adapted to: receive from a network node a downlink control information, DCI, that schedules a downlink transmission; detect a Radio Network Temporary Identifier, RNTI, used in the scheduling of the downlink transmission; select a time-domain resource allocation table from multiple different time-domain resource allocation tables based on the detected RNTI, wherein each of the different time domain resource allocation tables is defined by a plurality of entries specifying different combinations of starting orthogonal frequency division multiplexing, OFDM, symbol and duration in OFDM symbols for a time-domain resource allocation; and determine a time-domain resource allocation for the downlink transmission based on a time-domain resource allocation field in the DCI, the time-domain resource allocation field indicating an entry within the selected time-domain resource allocation table.
 10. The wireless device of claim 9, wherein the multiple different time-domain resource allocation tables relate to time-domain resource allocation for physical downlink shared channel, PDSCH, scheduling.
 11. The wireless device of claim 9, wherein the multiple different time-domain resource allocation tables comprise at least one pre-defined table with default values for the time domain resource allocation.
 12. The wireless device of claim 9, wherein the multiple different time-domain resource allocation tables comprise at least one radio resource control, RRC, configured table.
 13. The wireless device of claim 9, further adapted to: receive a physical downlink shared channel, PDSCH, on a time-domain resource corresponding to the determined time-domain resource allocation.
 14. The wireless device of claim 9, adapted to select the time-domain resource allocation table by selecting the time-domain resource allocation table based on at least one of a Control Resource Set, CORESET, and a search space used for scheduling the downlink transmission.
 15. The wireless device of claim 9, wherein a first table of the multiple different time-domain resource allocation tables comprises a different number of entries than a second table of the multiple different time-domain resource allocation tables, or wherein the multiple different time-domain resource allocation tables comprise a same number of entries. 